<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nader Alexan on Medium]]></title>
        <description><![CDATA[Stories by Nader Alexan on Medium]]></description>
        <link>https://medium.com/@naderalexan?source=rss-d4977411a25------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*an1TtUEe5yplxgTYGBWSdg.jpeg</url>
            <title>Stories by Nader Alexan on Medium</title>
            <link>https://medium.com/@naderalexan?source=rss-d4977411a25------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:08:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@naderalexan/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Comparison of AI agent for Software Engineering]]></title>
            <link>https://naderalexan.medium.com/comparison-of-ai-agent-for-software-engineering-8c4022714520?source=rss-d4977411a25------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c4022714520</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Nader Alexan]]></dc:creator>
            <pubDate>Thu, 03 Jul 2025 05:25:00 GMT</pubDate>
            <atom:updated>2025-07-03T05:25:00.074Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong>Disclaimer</strong>: I used AI agents to help me structure this post as well as provide comparisons between different tools</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CjSaUFSopH2KW9N5bMjP1A.png" /><figcaption>AI generated image by ChatGPT</figcaption></figure><h3>Introduction: AI Agents Are Changing How We Code</h3><p>In the past year, AI has gone from a clever autocomplete to a fully-fledged coding collaborator. Whether you’re sketching out an app idea on a web-based playground like <a href="https://bolt.new/">Bolt.new</a>, deep in the weeds of a complex Python project in <strong>PyCharm</strong>, or wrangling a CI script from the terminal with <strong>Claude Code</strong>, there’s now an AI agent built to fit your style.</p><p>But with so many tools — chatbots, IDE extensions, terminal-based agents, and “vibe-first” creative editors — it’s easy to feel overwhelmed. Each promises faster workflows, cleaner code, and smarter debugging. So which ones actually deliver? And more importantly, which one is right for <strong>you</strong>?</p><p>In this article, I break down today’s AI coding tools by category, comparing their strengths, limitations, and ideal use cases. Whether you’re a solo founder, a command-line wizard, or just AI-curious, you’ll leave with a clear picture of what to try — and why.</p><p>Let’s dive in.</p><h3>1. Vibe-first Web IDEs</h3><p><strong>Bolt.new</strong>, <strong>v0</strong>, <strong>Lovable.dev</strong></p><p><strong>What they are:</strong> <br>Lightweight, web-first editors where AI acts as a web development agent in a no-fuss environment. They require no previous understanding of software engineering to use.</p><p><strong>Best for:<br></strong>Prototyping, solo founders, creative coding, and demos.</p><p><strong>Pros:<br></strong>Instant setup, playful UX, chatty assistance.</p><p><strong>Cons:<br></strong>Limited features, bad extensibility (unless you do so manually — but that requires an understanding of software engineering), and generally not suited for medium to large production systems.</p><p><strong>Use-case<br></strong>When you want to experiment visually or get ideas quickly without local config. e.g. quick prototyping.</p><h3>2. IDEs with Integrated AI Agents (e.g. Cursor PyCharm, Webstorm, and Neovim)</h3><p><strong>What they are:<br></strong>For developers who live inside their IDEs, AI-integrated environments offer a deeply contextual and seamless experience. These tools don’t just autocomplete lines — they refactor functions, explain legacy code, and even help write tests or entire features based on your existing codebase.<br>Popular tools in this space include <strong>Cursor</strong> (an AI-first fork of VS Code), <strong>GitHub Copilot</strong>, <strong>Amazon CodeWhisperer</strong>, and <strong>Tabnine</strong>. Each integrates tightly with editors like VS Code, JetBrains, or IntelliJ, letting AI agents work <em>with</em> your local project, not just alongside it.</p><p><strong>Best for:<br></strong>These tools shine for full-time developers, teams maintaining large codebases, or anyone who prefers working within a robust editor. If you’re looking to speed up day-to-day tasks like writing boilerplate, fixing bugs, or navigating unfamiliar code, this category is where the heavy lifting happens.</p><p><strong>Pros:<br></strong>Deep integration with project files, version control, and terminal workflows.<br>Full access to context-aware suggestions (e.g., based on your project structure and open files).<br>Great for team-based workflows and production-grade applications.</p><p><strong>Cons:<br></strong>Heavier setup and sometimes steeper learning curves (e.g., managing plugins or billing tiers).<br>Some models still struggle with deeply abstract or domain-specific logic.<br>Performance and accuracy can vary depending on the language or tooling (e.g., Java support in Copilot vs Python in Cursor).</p><p>In short, IDE-integrated AI agents are built for <em>serious work</em> — less about brainstorming, more about accelerating the grind of real-world software development.</p><h3>3. CLI-Based Agentic Tools (e.g. Gemini CLI, Claude Code, Codex CLI, Aider)</h3><p>For developers who prefer living in the terminal, a new class of AI tools is emerging — <strong>CLI-based agentic coding assistants</strong>. These tools are designed to work like AI copilots for your shell, helping with everything from file generation to refactoring, without ever leaving the command line.</p><p>The main contenders in this space include:</p><p><strong>Claude Code</strong> (Anthropic), <strong>Gemini CLI</strong> (Google), <strong>Aider</strong> (open-source), <strong>Codex CLI</strong> (OpenAI-based tools and forks)</p><p><strong>Comparing the Tools:</strong></p><ul><li><strong>Claude Code</strong> is currently the strongest in natural language understanding and multi-step task planning. It’s ideal for code edits across files, project-wide refactoring, or debugging with minimal prompts. It supports git integration and structured planning, and early adopters praise its accuracy and tone.</li><li><strong>Gemini CLI</strong> is a sleek tool from Google’s Gemini family. It offers a polished experience and strong multimodal support, making it great for file scaffolding, basic coding tasks, and agent-style interactions. However, it’s not as precise with large refactors or highly specific instructions.</li><li><strong>Aider</strong> is a fast-growing open-source alternative that emphasizes direct git-based workflows. It’s lightweight, scriptable, and a favorite among developers who want fine-grained control over changes without relying on commercial APIs.</li><li><strong>Codex CLI</strong> tools (based on OpenAI’s models) vary in capability depending on implementation but typically offer code generation, editing, and chat-based command assistance. They’re highly customizable but may lag behind Claude in structured reasoning.</li></ul><h4>Best For:</h4><p>CLI-based tools are best suited for:</p><ul><li>Devs who prefer keyboard-first, minimal-GUI environments</li><li>Backend engineers, DevOps, or system-level coders</li><li>Scripting, automation, and infrastructure-as-code workflows</li></ul><h4>Pros</h4><ul><li><strong>Fast and focused</strong>: No IDE bloat — just fast iteration inside your terminal</li><li><strong>Context-rich</strong>: Many tools read your repo, git history, or file structure directly</li><li><strong>Automatable</strong>: Easily scriptable and agentic — ideal for repeatable workflows</li><li><strong>Great for pair-programming tasks</strong>: Like “refactor this file,” “explain this function,” or “add logging across modules”</li></ul><h4>Cons</h4><ul><li><strong>Learning curve</strong>: These tools often require manual configuration or understanding shell commands</li><li><strong>Limited visual feedback</strong>: If you’re a visual thinker, the lack of GUI can be disorienting</li><li><strong>Model dependency</strong>: Performance depends heavily on the backend model — Claude Opus tends to outperform others in complex workflows, but it’s not always available for free</li></ul><p><strong>Bottom Line</strong></p><p>If you’re comfortable in the terminal and want precise, AI-enhanced control over your repo without opening a full IDE, CLI agents are a powerful (and rapidly evolving) option. <strong>Claude Code</strong> leads in reasoning and edit quality, while <strong>Gemini CLI</strong> excels at usability and polish. For developers who want full control, <strong>Aider</strong> is a hidden gem.</p><h3>4. General/Chat LLMs for Code (ChatGPT, Claude, Gemini via API/chat)</h3><p>While not built into IDEs or terminals, <strong>chat-based AI models</strong> like <strong>ChatGPT</strong>, <strong>Claude</strong>, and <strong>Gemini</strong> have become indispensable tools for developers. Accessed through web apps, APIs, or mobile apps, these LLMs act like a highly knowledgeable coding buddy — ready to brainstorm, debug, explain, or even generate code snippets.</p><h4>Best For</h4><p>These tools are ideal when you need:</p><ul><li><strong>High-level code reasoning</strong> or system design discussions</li><li><strong>Debugging help</strong> for unclear errors or refactoring ideas</li><li><strong>Language or framework explanations</strong> (e.g. “What does this Rust macro do?”)</li><li><strong>Quick one-off scripts</strong> or small utilities without opening your full dev environment</li></ul><p>They’re also excellent companions for junior developers or non-technical founders who want to understand or communicate code better.</p><h4>Pros</h4><ul><li><strong>Conversational &amp; flexible</strong>: Perfect for exploring vague ideas or open-ended problems</li><li><strong>Language-agnostic</strong>: Great support for dozens of languages, from Python to Haskell</li><li><strong>Accessible anywhere</strong>: Use via browser, mobile, or integrated API</li><li><strong>No setup required</strong>: No plugins, installs, or repo indexing — just start asking questions</li><li><strong>Multi-purpose</strong>: Great for documentation help, test writing, prompt engineering, and more</li></ul><h4>Cons</h4><ul><li><strong>Limited context</strong>: Most chat models don’t have direct access to your project files (unless integrated through plugins or APIs)</li><li><strong>Copy-paste overhead</strong>: You’ll often need to shuttle code between your editor and the chat window</li><li><strong>Not ideal for multi-file refactors or dependency-heavy projects</strong></li><li><strong>May hallucinate</strong>: Especially on niche libraries, outdated syntax, or long codebases</li><li><strong>Performance varies</strong>: ChatGPT-4o and Claude Opus generally perform best in code reasoning, but model availability depends on platform and pricing</li></ul><h4>Model Comparisons</h4><ul><li><strong>ChatGPT-4o</strong> (OpenAI): Strong balance between reasoning, generation speed, and friendly UX. Great for generalists and frontend/backend code alike.</li><li><strong>Claude Opus</strong> (Anthropic): Best for in-depth code understanding, longer context windows, and clearer explanations. Developers love its calm, precise tone.</li><li><strong>Gemini </strong>(Google): Fast, smart, and capable — especially for Google Cloud tooling or app scaffolding, though sometimes less accurate in edge-case debugging.</li></ul><h4>Bottom Line</h4><p>If you want a powerful AI companion without leaving your browser — or you need natural language help across a range of coding tasks — chat-based LLMs are a versatile option. They’re not a full replacement for IDE agents, but they’re unbeatable for clarity, accessibility, and creativity.</p><h3>Summary</h3><ul><li>Solo founders / quick prototyping → Bolt.new, v0, lovable</li><li>Regular developers in IDEs → Copilot (balanced), Cursor (power)</li><li>Terminal-first developers → Claude Code, Gemini CLI</li><li>Chat-based help/debug/learning → ChatGPT, Claude, Gemini APIs</li></ul><h3>Final Thoughts</h3><p>AI agents for coding are now diverse: from lightweight vibe‑editors to full IDEs and CLI powerhouses. The right pick depends on <strong>your workflow</strong>, <strong>language needs</strong>, and <strong>how much context or control</strong> you want. Keep experimenting — this space is moving fast!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c4022714520" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to perform 1on1s with your direct reports]]></title>
            <link>https://naderalexan.medium.com/how-to-perform-1on1s-with-your-direct-reports-379a97caad33?source=rss-d4977411a25------2</link>
            <guid isPermaLink="false">https://medium.com/p/379a97caad33</guid>
            <category><![CDATA[managerialskills]]></category>
            <category><![CDATA[1on1-meeting]]></category>
            <category><![CDATA[managment]]></category>
            <category><![CDATA[manager-development]]></category>
            <category><![CDATA[software-engineer]]></category>
            <dc:creator><![CDATA[Nader Alexan]]></dc:creator>
            <pubDate>Mon, 18 Mar 2024 12:17:29 GMT</pubDate>
            <atom:updated>2024-03-18T12:17:29.801Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>One-on-one meetings, or 1-on-1s, are a critical activity for managers that should focus on meaningful discussions rather than technical details or status updates. These meetings are intended to be led by the employee, not the manager. In this article, we will explore various activities that managers should engage in to ensure high-quality 1-on-1s that truly benefit their direct reports.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kgq_agEyrsCrq170NNprhw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@airfocus?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">airfocus</a></figcaption></figure><h3>Activities</h3><p><strong>Active Listening</strong></p><p>In 1-on-1s, it is essential to prioritize active listening over talking. This approach helps managers gain a deeper understanding of their direct reports’ state of mind and allows employees to express any issues or concerns they may be facing. Active listening should serve as the cornerstone of successful 1-on-1 meetings. Managers should familiarize themselves with the principles of active listening and practice it consistently to ensure their direct reports feel heard and comfortable discussing matters with them</p><p><strong>Unblocking</strong></p><p>As a manager, it is your responsibility to identify and address any obstacles hindering the progress of your direct reports. Encourage your employees to proactively share any challenges they are facing, and actively work towards removing those obstacles as quickly as possible.</p><p><strong>Load Assessment</strong></p><p>Gain an understanding of your direct report’s workload, ensuring it is neither overwhelming nor too light. Strive to strike an appropriate balance that allows employees to perform optimally while avoiding burnout or boredom.</p><p><strong>Empowering</strong></p><p>Empower your direct reports by assigning tasks that slightly exceed their current skill level. This approach provides them with a sense of challenge and motivation. Assigning tasks that are too easy can lead to boredom, while overly challenging tasks may cause anxiety. Striking the right balance encourages growth and keeps employees motivated.</p><p><strong>Conflict and Issue Resolution</strong></p><p>Actively encourage your direct reports to discuss any conflicts or issues they may be experiencing. Often, individuals may not bring up such matters unless prompted directly. Addressing conflicts and issues early on allows for timely resolution and helps maintain a healthy work environment.</p><p><strong>Feedback</strong></p><p>1-on-1s provide an ideal opportunity to provide and request feedback, ideally on a biweekly basis. This ensures that your direct reports are aware of areas where they can improve and areas in which they are performing well. Additionally, it allows employees to provide feedback to you, creating a mutually beneficial feedback loop. Regular feedback during 1-on-1s ensures that no surprises arise during performance reviews, as feedback has been shared consistently over time.</p><p><strong>Check on personal progress/growth</strong></p><p>If a growth framework is in place for your direct reports, use 1-on-1s as an opportunity to follow up on their progress. If no framework currently exists, consider implementing one. This framework can help guide discussions around personal development and career growth.</p><p>Learn how to build one <a href="https://medium.com/@naderalexan/how-to-build-growth-frameworks-for-software-engineers-7068a9756237">here</a>.</p><h3>What to do when the employee has nothing to talk about</h3><p>There may be instances when employees come to a 1-on-1 meeting without specific topics to discuss, particularly in the early stages. In such cases, you can ask open-ended questions that encourage them to reflect on their experiences over the past two weeks. These questions can provide insights and pave the way for discussions related to the activities mentioned above. Here are some examples:</p><ul><li>How was last week for you?</li><li>Have you encountered any obstacles?</li><li>Is there anything positive you would like to see more of?</li><li>How can I best support you?</li></ul><h3>Conclusion</h3><p>When conducted effectively, 1-on-1s can be highly valuable for managers to gain insights into their employees’ work lives and provide optimal support in their day-to-day activities. It is crucial never to miss a 1-on-1 meeting, as it is the manager’s responsibility to schedule and prioritize these sessions. Cancelling should be avoided whenever possible, and rescheduling should be considered instead. It is better to conduct a meeting late than to skip it entirely.</p><p>Happy management!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=379a97caad33" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to build growth frameworks for software engineers]]></title>
            <link>https://naderalexan.medium.com/how-to-build-growth-frameworks-for-software-engineers-7068a9756237?source=rss-d4977411a25------2</link>
            <guid isPermaLink="false">https://medium.com/p/7068a9756237</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[Nader Alexan]]></dc:creator>
            <pubDate>Mon, 18 Mar 2024 08:47:39 GMT</pubDate>
            <atom:updated>2024-03-18T08:47:39.313Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Continuous learning is an important part of every software engineer’s career path, building a growth framework for everyone in your team can seem like a big task, but it doesn’t have to be when following the steps below. We will start by explaining the difference between mentorship and coaching then go into specific steps you can follow as a manager for approaching this task</p><h3>Mentorship vs coaching</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*OzO5AN064jUTAB_g" /><figcaption>Photo by <a href="https://unsplash.com/@medienstuermer?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Medienstürmer</a></figcaption></figure><p><strong>Mentorship</strong> (Directive) is direct work with mentee on topics where the mentor is an expert</p><blockquote>A mentor is an individual who imparts their wisdom, abilities, or past encounters in order to assist another individual in their personal growth and advancement.</blockquote><p><strong>Coaching</strong> (Non Directive) is providing constructive feedback and general direction based on coach’s experience e.g. coach is experienced in learning new tools and thus provides guidance to student on how to learn in general even in tools where coach is not an expert in.</p><blockquote>A coach is an individual who offers direction to a client regarding their objectives and aids them in realizing their maximum capabilities.How to build Growth Framework</blockquote><h3>Steps for building a growth framework</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rihopE6NicHy5KifJzL2eQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@joshua_j_woroniecki?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Joshua Woroniecki</a> on <a href="https://unsplash.com/photos/yellow-line-on-gray-asphalt-road-eUjT8kweNlg?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><h3>1. Identify areas of improvement</h3><p>Dedicate time to observe your engineers, assessing their work to pinpoint improvement areas. Keep detailed notes on their task performance, which can later serve as a basis for dialogue and development plans.</p><h3>2. Discuss areas of improvement with Engineers</h3><p>Engage with engineers to validate your observations. Involving them in the discussion promotes buy-in as they contribute to shaping their own improvement journey.</p><h3>3. Decide the type of Education you will be providing</h3><p><strong>Direct mentorship</strong></p><p>Engage in hands-on mentorship, offering a structured series of educational sessions interwoven with practical homework tasks</p><p><strong>Indirect mentorship + Coaching</strong></p><p>Pair the engineer with a subject matter expert for specific mentoring, while you provide regular coaching sessions to track progress and offer feedback.</p><p><strong>Resources + Coaching</strong></p><p>Compile educational materials (books, courses, practical projects) and supplement these resources with coaching sessions focused on the learning process.</p><h3>4. Setting Goals and Creating a Roadmap</h3><p>Work with engineers to set clear, achievable goals. Develop a roadmap with milestones to guide the learning process and measure progress.</p><h3>5. Providing Regular Feedback</h3><p>Offer regular, specific feedback to help engineers understand their progress and areas that require more attention. Feedback should be timely, relevant, and constructive.</p><h3>6. Encouraging Self-Reflection</h3><p>Encourage engineers to reflect on their experiences. Self-reflection is a powerful tool for personal development, helping them to internalize lessons and recognize their own growth.</p><h3>7. Fostering a Culture of Continuous Learning</h3><p>Promote an environment where learning is valued. Encourage knowledge sharing among team members and provide opportunities for engineers to learn from each other.</p><h3>8. Measuring Progress and Success</h3><p>Define metrics to measure the effectiveness of the mentorship and coaching efforts. Adjust strategies based on these insights to ensure continuous improvement.</p><h3>Conclusion</h3><p>Effective mentorship and coaching can accelerate the growth of software engineers, equipping them with the skills and knowledge to excel in their careers. By identifying areas of improvement, discussing them openly, setting clear goals, and providing structured learning opportunities, you can foster a culture of continuous professional development within your team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7068a9756237" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Innovation in Technical Hiring]]></title>
            <link>https://naderalexan.medium.com/innovation-in-technical-hiring-f2fe9e3b9c0c?source=rss-d4977411a25------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2fe9e3b9c0c</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[hiring-tips]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[hiring-process]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Nader Alexan]]></dc:creator>
            <pubDate>Sat, 02 Sep 2023 11:55:36 GMT</pubDate>
            <atom:updated>2023-09-02T11:55:36.050Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tv2p9HyjamuP07SxQKkrfg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jontyson?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jon Tyson</a></figcaption></figure><h3><strong>Introduction</strong></h3><p>Daily, hundreds if not thousands of software engineering experts receive emails, LinkedIn and Xing messages, calls, and other forms of communication from complete strangers, usually with a message along the lines of: “Dear X, Apologies, for the direct approach but I noticed your background and experience and I feel your profile would be a great fit for a new role I am recruiting for…”, the message usually goes on to describe a very vague position at an unnamed company, that is “the award-winning five-star leading new hip startup”. A large portion of these messages (based on personal experience and the experience of colleagues, not based on actual research done), get ignored, when not ignored, the recruiter goes on to request having a phone call to discuss the opportunity.</p><p>After working with recruiters from both sides (as a company and as a candidate), it became obvious that their success rate is rather low, specially when compared to online platforms connecting companies with candidates.</p><p>As a professional looking to grow his team, I have embarked on a research journey to try and figure out how to best approach the task of recruiting technical talent.</p><p>This paper represents the challenges, research, and solutions acquired from my journey.</p><h3>Methodology</h3><p><strong><em>Receiving and filtering applications</em></strong> The most common form of recruitment performed by organisations is post open positions on their websites or recruitment platforms. While this solution tends to dramatically decrease the effort and time required for having candidates in the recruitment pipeline, it can be rather inefficient for most organisations. Unless the organisation recruiting has a very strong reputation on the market, most of the applicants applying the online job posts are either not the correct fit (e.g. lacking the technical or soft skills required for the job) or applying for the wrong reasons (e.g. Migration, compensation, escaping current employer), and thus, the recruiter will spend the majority of their recruitment efforts in filtering applications — which, if your company is located in a vibrant city such as Berlin, that attracts a lot of people looking to immigrate — which can be in the hundreds, if not thousands. Out of these applications, a small portion will advance to the next step of interviews, and even smaller portion would eventually receive an offer.</p><p>Although recruiters can be hired for a rather reasonable compensation (due to the lack of need for formal education for such a position), it is more advisable to have fewer recruiters that are of high caliber. Assuming this is the case in your organisation, it would be wise to efficiently use their time.</p><p>Conclusion, for most organisations, posting job openings online can lead to a low conversion rate of applications to offers.</p><p><strong><em>Targeting</em></strong> Targeting is the proactive action of searching for high caliber candidates — whether on- or off-line — and persuading them to apply for the open positions. This method can be highly efficient when one sets proper criteria for choosing which potential candidate to approach and the how to do so effectively.</p><p>I personally have found Targeting to be the most effective option, so let’s dive deeper into it…</p><h3>Deep dive</h3><p><strong>Criteria</strong>: Depending on the organisation’s needs for the position at question, criteria can vary, however, there are usually high level umbrellas under which most criteria fall, such as, technical skills, culture, soft skills.</p><p>Using the aforementioned high level criteria, one can set rules upon which to choose which candidates to target, for instance, high reputation on technical websites (whether coding challenge websites, question and answers, or other), contributions to open source communities, previous experience in other organisations known for having strong technical teams, blog posts expressing the candidates opinions and point of view, and recommendations on business-oriented social networks (though these are usually driven by the candidate’s request to their peers for positive recommendations, read between the lines can be a good indicator of the candidate’s strengths).</p><p><strong>Approach</strong>: Upon identifying potential candidates for approaching, recruiter needs to find an approach that would spark interest in candidate for applying. It is utterly wasteful of time to find the right candidates but failing to convert them to interviewees. To best approach a candidate, it is advisable to understand their side of the story. Most high caliber candidates receive message_emails_calls on daily basis from other recruiters, fortunately for you, the reader, most recruiters fail miserably at this step. The following is a sample message that is far too common, it is to be used within the context for this study for demonstrating the mistakes.</p><p>“Dear X,</p><p>I really like your career progression over the past few years and think you would be a great fit for a position I am hiring for!</p><p>We have an exciting opportunity to work with one of the most dynamic multinational online companies in Germany.</p><p>They only hire the top 10% of candidates.</p><p>We have been retained to search for an Engineering Manager with Python background.</p><p>You will help deliver a next generation platform which will significantly expand their product offering.</p><p>This is a permanent opportunity based in Y.</p><p>How about a call this evening to discuss the position? Please send me your phone number, email address, and CV.</p><p>Kind regards,</p><p>Z</p><p>Director ”</p><p>Lack of proof and details: This message contains some rather bold statements (“hire the top 10% “, “most dynamic multinational online companies”, “ deliver a next generation platform”), however, there is nothing backing up these statements, there are no details about what the company is actually doing, what the position entails, what are the perks of this company, what the culture is like, etc.</p><p>Attempts at being vaguely nice: “I really like your career progression over the past few years and think you would be a great fit for a position I am hiring for!”, for anyone receiving such a message, they are aware that this is a copy pasted message, meant to be relatable to anyone receiving it. Try to be nice makes it feel dishonest to the receiver, as it seems like an attempt to show that the message is individualised.</p><p>Lack of job description and requirements: without these, it is not possible for the candidate to figure out whether or not they are suitable for the position and decide to move forward.</p><p>Call to action in first message: Without building interest in the position, the recruiter is asking the candidate to have a phone call, which, most of the time, is nothing more than a way for the recruiter to collect a pool of candidates to represent to companies (upon first contact) as a sales technique.</p><p><strong>A better message</strong>: “ X,</p><p>This is Y, I am representing company Z. We are building a product within the AI industry that does A, B, C (read more at: <a href="http://www.our-website.com/">www.our-website.com</a>).</p><p>We have a team of 10 developers (3 seniors, 3 midlevel, 1 Intern) and currently looking to expand the team with 2 senior Python developers to be able to deliver features at a higher rate.</p><p>We work in a collaborative, non-competitive environments using agile methodologies. Our teams are divided using the Spotify engineering model of squads and chapters (read more here: <a href="http://www.some-website.com/">www.some-website.com</a>).</p><p>Our clients are mostly in the automative industry, some of which are X, Y, Z.</p><p>I am approaching you today because I saw your project X on your Github account and given the quality of code in that project, I imagine you might be a proper fit for this role. You can find full description of the role in our job post here: <a href="http://www.job-post.com/">www.job-post.com</a></p><p>If you decide to apply for this position, the interview process would be as follows: 1. Screening technical and HR call (30 minutes): a chance to get to know each other informally 2. Homework task: a task meant to give you a feel of what you would be working on, on daily basis, as well as test your ability to architect code in a scalable manner 3. On-site test day: meet with the team, have discussions with different stakeholders, and have lunch with us! 4. Offer</p><p>To start with the first step, you can directly book a timeslot here: <a href="http://www.calendar-link.com/">www.calendar-link.com</a></p><p>If you want to ask any questions or get any clarification before moving forward, feel free to message me.</p><p>If you are not interested, please let me know.</p><p>Thanks, Y ”</p><p>Upon experimenting with messages that followed similar flow as the one before, this study has successfully received over 90% response rate.</p><h3><em>Process</em></h3><p><strong>First</strong> — Technical and HR screening: This call is split into parts, technical and HR. For the technical side, it is a rather easy set of questions meant to assess that this candidate has a solid understanding of the basics of software engineering, and assert that their experience in the field is relevant (contrary to a candidate mentioning ten years of software development experience, while in reality, it was more of project management then hands-on development). Sample questions here would be along the lines of, “explain how this framework handles x, y, z”, “What is the difference between Python 3 and 2”, “What is the use of Kubernetes”, “When does it make sense to use Microservices”, “What makes code of high or low quality in your opinion” For the HR side, use competency based questions and encourage the candidate to use the STAR technique for answers.</p><p>It is ideal to have a single interviewer per interview, as this allows for the interviewer and candidate to build rapport, makes the candidate less nervous, and does not require anyone to be splitting their attention.</p><p><strong>Second</strong> — Homework task: Depending on the position’s requirements this can vary to test different aspects of software engineering. It is best to ask the candidate to set a deadline for themselves, otherwise, this can take too long, or potentially postponed for long enough that the candidate gets an offer from another company during that time.</p><p><strong>Third</strong> — On-site test day: This is meant to accomplish three different aspects. First, simulating an actual work day. To do so, have the candidate work with other team members on a task similar to the day-to-day work. Second, asserting cultural fit. Have the candidate interact, informally, with very different employees, e.g. a project manager, the CEO, HR, Marketing, and then gather subjective feedback from the employees that interacted with this candidate. Third, additional personality and technical tests relevant to the position.</p><h3><strong>Discussion</strong></h3><p>Hiring software engineers is no easy task, due to a magnitude of issues, ranging from the fact that demand is higher than supply to the complexity of assessing technical skills. However, being systematically clear, transparent, direct, and most important humane in one’s approach can go a long way. This study has touched upon some high level points (while occasionally going into details) on how to systematically approach recruitment. However, further reading on the topics of emotional intelligence, decision making biases, and social psychology can be immensely helpful in achieving excellence within the field of recruitment.</p><p><strong>Liked this post?</strong> Have comments or suggestions on how to improve it? Please let me know in the comments or at <a href="/service/mailto:alexan.nader@gmail.com"><strong>alexan.nader@gmail.com</strong></a></p><p>Let’s connect over <a href="https://www.linkedin.com/in/naderalexan/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2fe9e3b9c0c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Make Meetings Great Again]]></title>
            <link>https://naderalexan.medium.com/make-meetings-great-again-6a50fd38a3cd?source=rss-d4977411a25------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a50fd38a3cd</guid>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[efficiency]]></category>
            <dc:creator><![CDATA[Nader Alexan]]></dc:creator>
            <pubDate>Tue, 07 Apr 2020 15:21:27 GMT</pubDate>
            <atom:updated>2020-04-07T15:21:27.892Z</atom:updated>
            <content:encoded><![CDATA[<p>Run meetings that neither suck nor waste time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*42LKtce7T16e8ssw" /><figcaption>Photo by <a href="https://unsplash.com/@shashanksahay?utm_source=medium&amp;utm_medium=referral">Shashank Sahay</a></figcaption></figure><h3><strong>Reserve time for preparation and follow-up</strong></h3><p>Every one puts meetings in their calendar, but do you also reserve time for preparation and follow-up? Or do you have back-to-back meetings and end up frequently improvising or coming up with solutions on the spot?</p><h3><strong>Send agenda items in advance</strong></h3><p>This allows participants to prepare, know what to expect, and make informed decision on whether or not to attend the meeting.</p><h3><strong>Assign roles</strong></h3><p>Every item on the agenda should be assigned to the person in charge of the related project. Additionally, one person must chair the meeting, s/he is required to facilitate discussions (asserting professionalism and non-deviation from topic), control timing, and making sure that everyone is heard, not just the extroverts.</p><h3><strong>Limit agenda topics</strong></h3><p>A meeting should focus on as few topics as possible, otherwise you risk loss of attention and too many participants that are not required for all the topics</p><h3><strong>Actionable items</strong></h3><p>Every item on the agenda discussed should end with clear steps on (1) action to be performed (2) Person(s) assigned to perform said action (3) How and to whom completion will be reported.</p><h3><strong>Follow-up on on actions</strong></h3><p>What use is a meeting if the topics discussed, and the actions agreed upon are not executed or executed incorrectly? Follow-up on actions!</p><blockquote>“Improvements in meeting effectiveness begin with canceling meetings.” -Fredmund Malik</blockquote><h3>Tools</h3><ol><li>Calculate how much your meeting costs using <a href="https://hbr.org/2016/01/estimate-the-cost-of-a-meeting-with-this-calculator">Harvard’s meeting calculator</a></li><li>Use a meeting planning checklist. Here is a <a href="https://hbr.org/2015/03/a-checklist-for-planning-your-next-big-meeting">great one</a> from Harvard.</li><li>Collect feedback and improve. Here is <a href="https://www.surveymonkey.com/r/Employee-Meeting-Feedback-Template">one</a> from SurveyMonkey.</li></ol><h3>Sources and further reading</h3><p>— “Managing Performing Living” By <a href="https://www.malik-management.com/#">Fredmind Malik</a></p><p>— <a href="https://hbr.org/">Harvard Business Review</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a50fd38a3cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 Time Management Tools for Software Developers]]></title>
            <link>https://naderalexan.medium.com/4-time-management-tools-for-software-developers-129ecb02c3f?source=rss-d4977411a25------2</link>
            <guid isPermaLink="false">https://medium.com/p/129ecb02c3f</guid>
            <category><![CDATA[flow]]></category>
            <category><![CDATA[focus]]></category>
            <category><![CDATA[concentration]]></category>
            <category><![CDATA[time-managment]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Nader Alexan]]></dc:creator>
            <pubDate>Tue, 18 Feb 2020 10:14:33 GMT</pubDate>
            <atom:updated>2020-07-24T06:50:40.049Z</atom:updated>
            <content:encoded><![CDATA[<h3>4 Time Management Tools You Can Start Using Today</h3><p>Managing your time seems like an elusive task, the requirements are simple but applying them is frequently hard to sustain. One solution could be to automate as much as possible with tools that frequently nudge you in the right direction.</p><p>The following are 4 tools you can start using right away to help you better be more effective in time management.</p><h3><strong>Microbreaks</strong></h3><p>— Tool: <a href="https://www.dejal.com/timeout/">TimeOut</a> (Mac) / <a href="http://www.workrave.org/">Work Rave</a> (Linux, Windows)</p><p><strong>Definition:</strong> A very short break (e.g. 15 seconds) every short block of work (e.g. 15 minutes), where one does <strong>not</strong> switch focus to another task, but just stops the current task, e.g. looking away from the screen and stretching.</p><blockquote>Microbreaks are regular, small, <em>biologically meaningful</em> breaks from being stuck in one position at work [2].</blockquote><p><strong>Benefits/Science:</strong> Study done by University of Illinois at Urbana-Champaign [1] shows that microbreaks dramatically improves one’s focus on prolonged tasks, adding to that, studies done by Baylor [3] and Standford [4] universities show that employees exercising microbreaks experience less headaches, lower back pain, and eyestrain compared to those who do not.</p><p><strong>Action: </strong>Experiment with 15–30 minutes blocks of work with 15–20 second microbreaks to find what is suitable for you. Ideally, use a tool (<a href="https://www.dejal.com/timeout/">TimeOut</a> or <a href="http://www.workrave.org/">Work Rave</a>) to automate this process for you</p><h3><strong>Time Analysis</strong></h3><p>— Tool: <a href="https://qotoqot.com/qbserve/">Qbserve</a> (Mac) / <a href="https://www.manictime.com/">Manic Time</a> (Linux, Mac, Windows) / <a href="https://www.rescuetime.com/">Rescue Time</a> (Browser)</p><p><strong>Definition: </strong>Measure and analyse what you spend your time on.</p><p><strong>Benefits/Science:</strong> Measuring how you spend your working hours can be very eye opening, specifically when you compare the time spent on tasks with the tasks’ priorities. For instance, are you spending multiple hours per day checking your email and responding to slack messages? Are you constantly context switching between working on a long-term feature and bug fixes? Favouring non-important-urgent tasks over important-non-urgent tasks is a far too common mistake, leaving one with important task not fulfilled until they become urgent. Furthermore, it helps figuring out when a task is going off track [5].</p><p><strong>Action: </strong>Measure the time spent on tasks (preferably using an automated tool such as <a href="https://qotoqot.com/qbserve/">Qbserve</a> or <a href="https://www.manictime.com/">Manic Time</a>) and before starting work everyday, analyse how you used your time the day before.</p><h3><strong>Concentration Sessions</strong></h3><p>— Tool: <a href="https://tomato-timer.com/">Tomato Timer</a> (Browser)</p><p><strong>Definition:</strong> Per block of time, work on a single task, this would be the opposite of multitasking.</p><p><strong>Benefits/Science: </strong>Multitasking kills productivity, this has been proven by multiple studies [10][11][12][13], avoid it at all costs and you might be able to achieve a <a href="https://en.wikipedia.org/wiki/Flow_(psychology)">state of Flow</a>.</p><p><strong>Action:</strong> Decide on what task you will focus on for the next block of time, start a timer (preferably using an automated tool such as <a href="https://tomato-timer.com/">Tomato Time</a>), put your phone on silent and turn it face down, disable other sources of notifications (e.g. browser, mail, chat apps -even work related ones such as Slack-). The only notification your computer should be able to show, is the one from your timer. Bonus points: remove anything that shows time from your sight so you do not get distracted by how much of the current session is left, instead, purely focus on the task at hand.</p><h3><strong>Concentration on a few topics</strong></h3><p>— Tool: <em>Your own choices</em></p><p><strong>Definition:</strong> Concentrating on a few topics at any given time.</p><p><strong>Benefits/Science:</strong> Extensive research done by the psychologist George Miller attempted to measure the “channel capacity” of the mind, with the conclusion that the mind can associate about seven different labels with continuous stimuli. Read more at [7][8][9].</p><p><strong>Action:</strong> Are you doing feature development, bug fixes, and participating in the roadmap of your company’s product? Sounds great, make sure that the total number of different tasks is less than or equal to seven (each feature/bug is counted separately). Write them down on a small paper, and put it somewhere visible on your workspace. Bonus: helps with explanation to others when you say “No” to other tasks, “sorry boss-man, I cannot take on this task at the moment as I have another seven that I am focusing on and I would not want to deliver lower quality work by taking on more than I can handle.”</p><h3>Closing notes</h3><p>This is a high level view of the principles and tools, there is much much more to explore, if you are interested in the topic, checkout the source below, and checkout <a href="https://dspace3-labs.atmire.com/bitstream/handle/123456789/6649/file14678.pdf?sequence=1">this literature review</a> [6] on the topic</p><h3>Give me Feedback</h3><p>Do you have <strong>feedback</strong> for me? Regardless if it is positive or negative, <strong>let me know</strong> (comments, <a href="https://www.linkedin.com/in/naderalexan/">LinkedIn</a>, email: <a href="/service/mailto: alexan.nader@gmail.com">alexan.nader@gmail.com</a>). See photo below for relevance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2egnpfxk5jcEvJ-tG0BmwA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@wwwynand?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Wynand van Poortvliet</a></figcaption></figure><h3><strong>Sources</strong></h3><ol><li>University of Illinois at Urbana-Champaign. “Brief diversions vastly improve focus, researchers find.” <em>ScienceDaily</em>. ScienceDaily, 8 February 2011. &lt;www.sciencedaily.com/releases/2011/02/110208131529.htm&gt;.</li><li>Ingraham, Paul, “Microbreaking”, <em>painscience, </em>12 May 2018. &lt;<a href="https://www.painscience.com/articles/microbreaking.php">https://www.painscience.com/articles/microbreaking.php</a>&gt;</li><li>Hunter, E. M., &amp; Wu, C. (2016). Give me a better break: Choosing workday break activities to maximize resource recovery. <em>Journal of Applied Psychology, 101</em>(2), 302–311. &lt;<a href="https://psycnet.apa.org/doi/10.1037/apl0000045">https://doi.org/10.1037/apl0000045</a>&gt;</li><li>Waltz, P. R. (2016). Experiencing recovery at work: Energetic benefits of social media micro-breaks. <em>Journal of Organizational Behavior</em>, 38(1), 28–44.</li><li>Mackenzie, R. Alec. <em>The time trap : the classic book on time management / Alec Mackenzie and Pat Nickerson. — 4th ed</em>. Amacom, 2009.</li><li>Claessens, B., van Eerde, W., Rutte, C. and Roe, R. (2007), “A review of the time management literature”, <em>Personnel Review</em>, Vol. 36 №2, pp. 255–276. &lt;<a href="https://doi.org/10.1108/00483480710726136">https://doi.org/10.1108/00483480710726136</a>&gt;</li><li>Hébert, R. (2006). The Miller’s tale: A genealogy of the father of the cognitive revolution. APS Observer 19(6).</li><li>Cohen-Cole, J. (2007). Instituting the science of mind: intellectual economies and disciplinary exchange at Harvard’s Center for Cognitive Studies. British Journal of the History of Science 40(4), pp. 567–597.</li><li>Eminent psychologists of the 20th century. (July/August, 2002). <em>Monitor on Psychology, 33(7), p.29.</em></li><li>MANHART, KLAUS. “The Limits of Multitasking.” <em>Scientific American Mind</em>, vol. 14, no. 5, 2004, pp. 62–67., &lt;<a href="http://www.jstor.org/stable/24997557.">www.jstor.org/stable/24997557.</a> Accessed 18 Feb. 2020.&gt;</li><li>Odmar Neumann and Andries F. Sanders, 1996, “Attention. Series 3: Handbook of Perception and Action.” <em>Harcourt.</em></li><li>John R. Anderson. W. H. Freeman and Company, 1999, “Cognitive Psychology and Its Implications. Fifth edition.”</li><li>Joshua S. Rubinstein, David E. Meyer and Jeffrey E. Evans, August 2001, “Executive Control of Cognitive Processes in Task Switching”, <em>Journal of Experimental Psychology — Human Perception and Performance, Vol. 27, №4, pages 763–797.,</em> &lt;<a href="http://www.apa.org/journals/xhp/">www.apa.org/journals/xhp/</a> press_releases/august_2001/xhp274763.html&gt;</li></ol><p><strong>You looked at the sources!</strong> or just randomly scrolled down, either way, here is a photo of my Pug for the great job you did by looking at sources!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c5S6I_6HbA33zBEVF-n9MQ.jpeg" /><figcaption>Photo by Nader Alexan of Kimchi, the best pug in the world, well, at least in my apartment.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=129ecb02c3f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Positive Habits]]></title>
            <link>https://medium.com/3yourmind-team/building-positive-habits-b2a3035e5e2c?source=rss-d4977411a25------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2a3035e5e2c</guid>
            <category><![CDATA[life-improvement]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[habit-building]]></category>
            <dc:creator><![CDATA[Nader Alexan]]></dc:creator>
            <pubDate>Sat, 06 Jul 2019 05:46:27 GMT</pubDate>
            <atom:updated>2019-07-06T05:59:27.370Z</atom:updated>
            <content:encoded><![CDATA[<h3>How are habits formed?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O7Qjo8H_Y_ygTsbB_txgyQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@patrickian4?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Patrick Fore</a></figcaption></figure><p>It’s a hot summer day in Berlin, I am cycling alongside the spree, enjoying the fresh breeze, when I see a huge billboard for Heinken, with a glass full to the rim with what looks like very cold and refreshing beer (<em>CUE</em>).</p><p>I think to myself, gosh, it would probably taste amazing after I’ve been cycling for a few KMs now to stop and have a cold beer (<em>CRAVING</em>).</p><p>Five minutes later, I find myself searching for an biergarten to sit down and grab myself a cold one (<em>RESPONSE</em>).</p><p>Another five minutes and I am enjoying the feeling of cold beer down my throat (<em>REWARD</em>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/682/1*ruzVhlMliZE-CIm0eCuE-Q.png" /></figure><p>To form any habit, you need to create a cue, craving, and reward — Vice versa, to kill a bad habit, kill the cue, craving, reward, or all three.</p><p><strong>Cue — </strong>Let’s say you want to start meditating everyday, you need to start by creating a cue, (e.g. notification on your phone, post it on your laptop, or better yet, habit chaining — will explain in the coming paragraphs)</p><p><strong>Craving —</strong> This one is tricky, you see when you start meditating the first few weeks, you probably do not crave it, as you have yet to experience the reward that comes from constantly meditating. This can be solved by two ways, both related to reward. Read on.</p><p><strong>Reward — </strong>Either create an extrinsic reward, such as giving yourself something you enjoy (e.g. a piece of chocolate, positive self-talk) or better yet, enjoy the intrinsic reward at the end of each meditation session by taking a few minutes to do nothing. Just focus on the positive effects of meditation, the feeling of relaxation, the clear mind, and more importantly, be very conscious about how you feel, possibly write it down. This will pour back into the craving as you continue to meditate everyday.</p><h3>The most common misconception about habits</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e530ehvEkd3D1l4Nog3qhw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@icons8?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Icons8 tea</a></figcaption></figure><p>Time. Lots of it.</p><p>According to a <a href="https://onlinelibrary.wiley.com/doi/abs/10.1002/ejsp.674">study</a> published in the European Journal of Social Psychology, it takes a median of 66 repetitions for a habit to become automatic. This does not oppose the earlier findings of Maxwell Maltz in his book <a href="https://www.amazon.de/dp/0671700758/ref=as_li_qf_sp_asin_il_tl?ie=UTF8&amp;linkCode=gs2&amp;linkId=6DQ32IRAG3LU4PKA&amp;creativeASIN=0671700758&amp;tag=jamesclear0c-21&amp;creative=9325&amp;camp=1789">Psycho-Cybernetics</a>, as he mentions a minimum of 21 days, not an average of 21 days.</p><p>So what usually happens, you start off with one habit, a couple of weeks later, you’re super happy with the results and start attempting to add other habits to your life. This fails. Always.</p><p>The reason this fails, is that by the first few weeks, it is still not an automatic habit in your brain, and it takes quite a lot of effort to actually reach the point of automaticity, so if you start adding more habits before the first one has reached automaticity, you will end up breaking all of them. Try it.</p><h3>Difficulty versus time</h3><p>A very interesting phenomena tends to appear when you start adding a new habit to your life, the difficulty of performing the habit varies in an inconsistent manner over the first few weeks:<br>Days 1–3: You are excited to be adding a positive habit, and it seems quite easy to get yourself to do it</p><p>Day 4: Hard, you must push yourself not to slack</p><p>Days 5–10: It slowly becomes easier</p><p>Days 11–25: It seems easy, sometimes too easy, that you just postpone it through the day, until you end up going to bed without doing it. Tricky.</p><p>Days 25–66: It slowly starts becoming automatic.</p><p>Power through, otherwise, you will easily fall.</p><h3>Keynote Habits</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZiWTLjnGjN6ol7E5PA-4Yg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@ilyailford?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Ilya Ilford</a></figcaption></figure><p>There are certain habits that tend to automatically get you to build other positive habits in your life, for instance have you ever seen someone start doing sports everyday, then automatically started eating healthier, have a sleep schedule, start meditating more, spending more time on social activities….and so on?</p><p>Well, that’s a keynote habit at play, unlike for instance a positive habit such as drinking 8 glasses of water per day, there are habits such as sports, meditation, and diet, that tend to bring along a lot of other positive aspects to your life automatically, it is quite wise to start your positive habit building journey with such habits.</p><h3>Environment and other tools</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t3A-s2eExektSb4S48r0FQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@toddquackenbush?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Todd Quackenbush</a></figcaption></figure><p>There are changes in your day-to-day environment that can make building the desired habits extensively easier, for instance:</p><ol><li>Surround yourself with others on the same journey as your own, prime examples of the wild success of such concept is AA.</li><li>Remove distractions and oppositions, e.g. if you are trying to eat healthy, but keep your fridge packed with red meats, or frequently go out with friends to fast-food restaurants, well, you are just making it harder for yourself.</li><li>Invest upfront. You are more likely to go to a gym if you are paying a monthly fee for it and subscribing to training plan, instead of planning to go workout in the park, where doing it today or next month, does not change much</li><li>Make it public. Tell people around you about your plans to start meditating everyday, this will allow for a certain level of accountability when they ask if you’ve been doing it</li><li>Create defence systems. If you are trying to stop smoking, make a plan on what you will do when offered a cig, what you will do when you feel a craving, what you will do when get weak once and do smoke, will it just be the end of your attempt, or just a bump in the road?</li><li>Journal. Write about your experience, everyday, this allows you to not exaggerate the difficulty of the habit, nor forget about the rewards.</li><li>Set a clear reason why you are doing this, what you want to accomplish, and how you will do it exactly.</li><li>Habit chaining: you probably have a lot of habits already ingrained in your day-to-day life, maybe it is drinking coffee every morning, or taking your dog for a walk after breakfast. Habit chaining is when you chain your new habit to an existing habit, thus making the old habit, the cue for the new habit. e.g. Meditate right after your morning coffee.</li><li>Make it as easy as possible. If you want to start running everyday, make it 3 minutes initially everyday and then work your way up as you feel more comfortable with it, this way, your head does not beat you down with thoughts like: Oh I don’t have time for it, or this would be too exhausting and I have not ran in ages, etc.</li></ol><h3>Wrap up</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xYIgjtYKNgbLnwMdsqz8bg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@sonance?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Viktor Forgacs</a></figcaption></figure><p>Building habits is not an easy task, but is a manageable one. Set clear goals, create a habit loop, give it time, supplement your efforts with the right environment, and give it time.</p><p>Oh, and best to start with a keynote habit ;).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2a3035e5e2c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/3yourmind-team/building-positive-habits-b2a3035e5e2c">Building Positive Habits</a> was originally published in <a href="https://medium.com/3yourmind-team">3YOURMIND Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Scraping in Python]]></title>
            <link>https://medium.com/dreidev/web-scraping-in-python-e07fba0a1663?source=rss-d4977411a25------2</link>
            <guid isPermaLink="false">https://medium.com/p/e07fba0a1663</guid>
            <category><![CDATA[selenium]]></category>
            <category><![CDATA[web-crawler]]></category>
            <category><![CDATA[scraping]]></category>
            <category><![CDATA[web-crawling]]></category>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[Nader Alexan]]></dc:creator>
            <pubDate>Sun, 22 Apr 2018 12:54:42 GMT</pubDate>
            <atom:updated>2018-04-22T13:26:55.903Z</atom:updated>
            <content:encoded><![CDATA[<p>Motivation — At the time of writing this post, there are 1,314 posts on Upwork for web scraping projects. As I contacted a few of them and checked their requirements, it became quite obvious that their needs are not complex but rather extensive.</p><p>I started building one scraper at a time, targeting the websites the clients wanted to scrape. After three happy clients, I realized that a simple format for defining the data (data to be scrapped) and making the script generic allowed me to cut the development time from a few hours to a few minutes.</p><h3><strong>Implementation</strong></h3><p>Basic scraping follows the steps:</p><ol><li>Requesting the page — <a href="http://docs.python-requests.org/en/master/">requests library</a>, <a href="https://www.seleniumhq.org/">selenium</a></li><li>[optional] Asserting that data is loaded — custom script</li><li>Parsing the HTML — <a href="https://www.crummy.com/software/BeautifulSoup/bs4/doc/">BeautifulSoup library</a></li><li>Retrieving the required data — <a href="https://www.crummy.com/software/BeautifulSoup/bs4/doc/">BeautifulSoup library</a></li><li>Storing the data — custom script</li></ol><p>Each step on it’s own is quite easy to implement, it is the creation of a reusable script covering most of the cases that can be slightly tricky.</p><p><strong>Requesting the page — </strong><a href="http://docs.python-requests.org/en/master/"><strong>requests library</strong></a><strong>, </strong><a href="https://www.seleniumhq.org/"><strong>selenium</strong></a></p><p>Using the requests library is the easiest way to go. Example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6af0becd130900398c66705459d76fa7/href">https://medium.com/media/6af0becd130900398c66705459d76fa7/href</a></iframe><p>Attempt to use this with any website that loads data dynamically and you will quickly see the issue here. It requests the page as is, without allowing any JS to run on the page. Solution? Use selenium.</p><p>The code now looks this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/afed286921da3b0f0acfd87e51e631d2/href">https://medium.com/media/afed286921da3b0f0acfd87e51e631d2/href</a></iframe><p><strong>[optional] Asserting that data is loaded — custom script</strong></p><p>To assert that the data is loaded, a simple check for the existence of certain tags or text can be sufficient. For instance, consider the case of <a href="https://careers.google.com/jobs#t=sq&amp;q=j&amp;li=20&amp;l=false&amp;jlo=en-US&amp;jl=52.52000659999999%3A13.404953999999975%3ABerlin%2C+Germany%3ADE%3A%3A18.39444871486873%3ALOCALITY%3A%3A%3A%3A%3A%3A&amp;jld=20&amp;j=Python&amp;">Google Careers Search Results</a> where the results are loaded dynamically. Example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/45f0eeffbd63931faf789e5add83c1d1/href">https://medium.com/media/45f0eeffbd63931faf789e5add83c1d1/href</a></iframe><p><strong>Parsing the HTML — </strong><a href="https://www.crummy.com/software/BeautifulSoup/bs4/doc/"><strong>BeautifulSoup library</strong></a></p><p>Parsing the html was already done in the previous step for checking that the data is loaded in the page, however, since the previous step is optional, parsing the HTML should be a step on its own.</p><p>For parsing HTML is python, there is the <a href="https://www.crummy.com/software/BeautifulSoup/bs4/doc/">BeautifulSoup</a> library, which is both easy to use and rather powerful. It takes one line of code to parse the HTML. Example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e8faecfb16b78812a7c4d7d0a5009fe8/href">https://medium.com/media/e8faecfb16b78812a7c4d7d0a5009fe8/href</a></iframe><p><strong>Retrieving the required data — </strong><a href="https://www.crummy.com/software/BeautifulSoup/bs4/doc/"><strong>BeautifulSoup library</strong></a></p><p>Retrieving data is straight forward using BeautifulSoup’s function find(). Example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e1d0aabc844debea6bf9a484169ceaae/href">https://medium.com/media/e1d0aabc844debea6bf9a484169ceaae/href</a></iframe><p><strong>Putting Everything Together</strong></p><p>If you’ve made it this far, you realize that implementing your own scraper in python is a pretty easy task, the challenge comes when you want to put it all together to get a generic scraper that you can use over and over again in order to finish scraping jobs in tenth of the time. That’s exactly what I went on to do, however, going through all the implementation details here would be an overkill, as well as a duplication of the scraper’s documentation (the one I built).</p><p>You can find the generic scraper with its documentation in this <a href="https://github.com/naderalexan/generic_scrapper">Github repository</a>.</p><p>On the other hand, if you choose to write your own based on the knowledge within this article, then you need to create a format for representing the tags that contain the data you want, in my case, I re-used the one that BeautifulSoup uses, with additions that you can read about in the documentation for my <a href="https://github.com/naderalexan/generic_scrapper/blob/master/scrapper.py">scraper function here</a></p><h3>Conclusion</h3><p>Web scraping can be trivial and get complex, this article attempts to explain how to build a slightly powerful, but mostly generic scraper that can be used for most of the scraping that is requested from the everyday developer, as for the more complex ones, I would recommend checking out some of the scraping libraries such as <a href="https://scrapy.org/">Scrapy</a>, or build your own.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e07fba0a1663" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dreidev/web-scraping-in-python-e07fba0a1663">Web Scraping in Python</a> was originally published in <a href="https://medium.com/dreidev">DREIDEV</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>