<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Engineering Leadership on Omid Farhang</title><link>https://omid.dev/tags/engineering-leadership/</link><description>Recent content in Engineering Leadership on Omid Farhang</description><image><title>Omid Farhang</title><url>https://omid.dev/images/bio-photo-150x150.jpg</url><link>https://omid.dev/images/bio-photo-150x150.jpg</link></image><generator>Hugo -- 0.165.0</generator><language>en-US</language><copyright>2026 Omid Farhang | All rights reserved.</copyright><lastBuildDate>Mon, 14 Sep 2026 00:40:00 +0330</lastBuildDate><atom:link href="https://omid.dev/tags/engineering-leadership/index.xml" rel="self" type="application/rss+xml"/><atom:link href="https://pubsubhubbub.appspot.com/" rel="hub"/><item><title>Essential Skills When Generation Is Cheap</title><link>https://omid.dev/2026/09/14/essential-skills-when-generation-is-cheap/</link><pubDate>Mon, 14 Sep 2026 00:40:00 +0330</pubDate><guid>https://omid.dev/2026/09/14/essential-skills-when-generation-is-cheap/</guid><description>The skill list did not get a new bubble called AI. The senior job changed: you own output you did not type, you review at a higher altitude, and you decide where generation does not belong.</description></item><item><title>I Interview Frontend Hires for Other Companies</title><link>https://omid.dev/2026/09/09/i-interview-frontend-hires-for-other-companies/</link><pubDate>Wed, 09 Sep 2026 03:00:00 +0330</pubDate><guid>https://omid.dev/2026/09/09/i-interview-frontend-hires-for-other-companies/</guid><description>How I interview frontend candidates for a team that is not mine — intake with their lead, choosing the real level, and why I now weigh architecture, ownership, and AI judgment over syntax recall.</description></item><item><title>Have Influence Without Becoming the Backdoor</title><link>https://omid.dev/2026/08/19/have-influence-without-becoming-the-backdoor/</link><pubDate>Wed, 19 Aug 2026 00:30:00 +0330</pubDate><guid>https://omid.dev/2026/08/19/have-influence-without-becoming-the-backdoor/</guid><description>Cross-team trust is a career asset. Unofficial ownership is a career trap. How a senior brings feedback, protects UX, and stays on the team&amp;#39;s side of the board.</description></item><item><title>Channel the Scout, Keep the Seat</title><link>https://omid.dev/2026/08/18/channel-the-scout-keep-the-seat/</link><pubDate>Tue, 18 Aug 2026 00:30:00 +0330</pubDate><guid>https://omid.dev/2026/08/18/channel-the-scout-keep-the-seat/</guid><description>Do not punish cross-team friendliness. Give the scout an official boundary: shared intake, no silent commitments, and polish on a budget.</description></item><item><title>When the Best Communicator Becomes the Backdoor</title><link>https://omid.dev/2026/08/17/when-the-best-communicator-becomes-the-backdoor/</link><pubDate>Mon, 17 Aug 2026 00:30:00 +0330</pubDate><guid>https://omid.dev/2026/08/17/when-the-best-communicator-becomes-the-backdoor/</guid><description>On a small development team, the senior who talks to other teams may be the most valuable person in the room—until influence becomes unofficial ownership.</description></item><item><title>The Frontend Is a Privileged System Now</title><link>https://omid.dev/2026/08/15/the-frontend-is-a-privileged-system-now/</link><pubDate>Sat, 15 Aug 2026 23:50:00 +0330</pubDate><guid>https://omid.dev/2026/08/15/the-frontend-is-a-privileged-system-now/</guid><description>The browser is untrusted, but the system that builds and delivers the frontend is not. Install hooks, CI identities, and release credentials make frontend delivery a production trust boundary.</description></item><item><title>After the Zoom-Out: A Playbook for Staying Current Without Burning Out</title><link>https://omid.dev/2026/06/25/after-the-zoom-out-a-playbook-for-staying-current/</link><pubDate>Thu, 25 Jun 2026 10:00:00 +0330</pubDate><guid>https://omid.dev/2026/06/25/after-the-zoom-out-a-playbook-for-staying-current/</guid><description>Part two of the ecosystem blind spot series. The first post named the feeling; this one is the playbook — pain-driven discovery, pattern recognition, technology reconnaissance, and the habits that keep experienced engineers ahead of expensive gaps.</description></item><item><title>The Zoom-Out: When 15 Years of Code Meets the "Ecosystem Blind Spot"</title><link>https://omid.dev/2026/02/25/the-zoom-out-when-15-years-of-code-meets-the-ecosystem-blind-spot/</link><pubDate>Wed, 25 Feb 2026 22:22:05 +0330</pubDate><guid>https://omid.dev/2026/02/25/the-zoom-out-when-15-years-of-code-meets-the-ecosystem-blind-spot/</guid><description>A senior developer reflects on the ecosystem blind spot after 15 years of coding, exploring how to regain perspective and stay current.</description></item><item><title>The Ethics of Legacy Code: Why Rewriting is Often a Mistake</title><link>https://omid.dev/2025/12/27/ethics-of-legacy-code/</link><pubDate>Sat, 27 Dec 2025 02:23:11 +0330</pubDate><guid>https://omid.dev/2025/12/27/ethics-of-legacy-code/</guid><description>Explore the social and ethical implications of legacy code and why &amp;#39;rewriting from scratch&amp;#39; is often a failure of empathy.</description></item><item><title>The Cost of Consistency: Avoiding Design System Bottlenecks</title><link>https://omid.dev/2025/12/25/cost-of-consistency-design-systems/</link><pubDate>Thu, 25 Dec 2025 02:21:24 +0330</pubDate><guid>https://omid.dev/2025/12/25/cost-of-consistency-design-systems/</guid><description>Lessons learned from building a comprehensive Angular-based design system and how to avoid the rigidity trap and abstraction tax.</description></item><item><title>Mentorship in Tech: How to Be an Effective Mentor and Mentee</title><link>https://omid.dev/2024/07/14/mentorship-in-tech-how-to-be-an-effective-mentor-and-mentee/</link><pubDate>Sun, 14 Jul 2024 16:56:35 +0330</pubDate><guid>https://omid.dev/2024/07/14/mentorship-in-tech-how-to-be-an-effective-mentor-and-mentee/</guid><description>&lt;p&gt;Mentorship is a cornerstone of professional growth and development, particularly in the fast-paced and ever-evolving tech industry. Whether you&amp;rsquo;re a seasoned professional or just starting your career, engaging in a mentor-mentee relationship can provide invaluable insights, support, and opportunities for both personal and professional advancement. This blog post explores the benefits of mentorship in tech and offers practical guidelines for both mentors and mentees to maximize their relationships.&lt;/p&gt;
&lt;h2 id="the-importance-of-mentorship-in-tech"&gt;The Importance of Mentorship in Tech&lt;/h2&gt;
&lt;h3 id="accelerated-learning-and-skill-development"&gt;Accelerated Learning and Skill Development&lt;/h3&gt;
&lt;p&gt;One of the most significant benefits of mentorship is the accelerated learning curve it provides. Mentors can share their knowledge, experience, and insights, helping mentees navigate complex technical concepts and industry trends more quickly than they might on their own. This hands-on guidance can be particularly valuable in the tech industry, where new technologies and methodologies emerge rapidly.&lt;/p&gt;</description></item><item><title>Avoiding Framework Lock-in: A Frontend Team Leader's Guide</title><link>https://omid.dev/2024/07/04/breaking-free-from-framework-constraints/</link><pubDate>Thu, 04 Jul 2024 01:50:50 +0330</pubDate><guid>https://omid.dev/2024/07/04/breaking-free-from-framework-constraints/</guid><description>&lt;p&gt;As a frontend team leader, one of your most crucial responsibilities is ensuring your team remains adaptable and forward-thinking in an ever-evolving technological landscape. While standardizing on a single framework can provide short-term efficiency, it risks limiting your team&amp;rsquo;s growth and flexibility in the long run. Let&amp;rsquo;s explore strategies to avoid this pitfall, complete with real-world examples.&lt;/p&gt;
&lt;h2 id="focus-on-core-principles"&gt;Focus on Core Principles&lt;/h2&gt;
&lt;p&gt;At the heart of frontend development lie the fundamental web technologies: HTML, CSS, and JavaScript. These form the bedrock upon which all frameworks are built. By emphasizing mastery of these core technologies, you equip your team with transferable skills that transcend any single framework.&lt;/p&gt;</description></item><item><title>Effective Communication for Developers: Bridging the Gap Between Technical and Non-Technical Teams</title><link>https://omid.dev/2024/06/27/bridging-the-gap-between-technical-and-non-technical-teams/</link><pubDate>Thu, 27 Jun 2024 22:32:40 +0330</pubDate><guid>https://omid.dev/2024/06/27/bridging-the-gap-between-technical-and-non-technical-teams/</guid><description>&lt;p&gt;In the modern workplace, developers often find themselves at the intersection of technology and business. While the technical prowess required to build and maintain software systems is crucial, the ability to communicate effectively with non-technical stakeholders is equally important. This blog post aims to provide developers with tips and strategies to bridge the communication gap between technical and non-technical teams, ensuring smoother collaborations and more successful projects.&lt;/p&gt;
&lt;h2 id="understanding-the-importance-of-effective-communication"&gt;Understanding the Importance of Effective Communication&lt;/h2&gt;
&lt;p&gt;Effective communication is the backbone of any successful project. When developers can clearly convey their ideas, challenges, and progress to non-technical stakeholders, it fosters a collaborative environment where everyone is aligned towards common goals. Here are some key reasons why effective communication is vital:&lt;/p&gt;</description></item><item><title>Conflict Resolution in Tech Teams: Advanced Mediation Techniques</title><link>https://omid.dev/2024/06/10/conflict-resolution-in-tech-teams-advanced-mediation-techniques/</link><pubDate>Mon, 10 Jun 2024 00:01:18 +0330</pubDate><guid>https://omid.dev/2024/06/10/conflict-resolution-in-tech-teams-advanced-mediation-techniques/</guid><description>&lt;p&gt;Conflict is an inevitable part of any workplace, and tech teams are no exception. Differences in opinions, approaches, and personal styles can lead to friction. However, when managed effectively, conflict can be a catalyst for growth, innovation, and stronger teamwork. This blog post explores advanced techniques for resolving conflicts within tech teams, covering mediation strategies, active listening, and fostering a collaborative environment.&lt;/p&gt;
&lt;h2 id="understanding-conflict-in-tech-teams"&gt;Understanding Conflict in Tech Teams&lt;/h2&gt;
&lt;p&gt;Tech teams are often composed of individuals with diverse skills, backgrounds, and perspectives. While this diversity is a strength, it can also lead to misunderstandings and disagreements. Common sources of conflict in tech teams include:&lt;/p&gt;</description></item><item><title>Building Resilient Teams: Recover From Setbacks and Keep Shipping</title><link>https://omid.dev/2024/06/06/building-resilient-teams/</link><pubDate>Thu, 06 Jun 2024 22:08:53 +0330</pubDate><guid>https://omid.dev/2024/06/06/building-resilient-teams/</guid><description>Team resilience is not individual grit. It is the capacity to absorb a bad sprint, a failed launch, or a reorg—and return to steady delivery without burning people out.</description></item><item><title>Is Building Your Own Design System Worth It? Best Practices, Key Considerations and Real-World Example</title><link>https://omid.dev/2024/06/02/is-building-your-own-design-system-worth-it/</link><pubDate>Sun, 02 Jun 2024 17:17:02 +0330</pubDate><guid>https://omid.dev/2024/06/02/is-building-your-own-design-system-worth-it/</guid><description>&lt;p&gt;In the ever-evolving landscape of web development, the question of whether to build and develop your own design system is a common one. As design systems become more integral to creating cohesive, scalable, and efficient applications, it&amp;rsquo;s crucial to weigh the benefits and challenges. This blog post delves into the worthiness of developing a custom design system, best practices for building one, when it&amp;rsquo;s needed, and the role of JavaScript frameworks like Angular. Additionally, we&amp;rsquo;ll explore which development teams should be involved in this process and provide a real-world example for clarity.&lt;/p&gt;</description></item><item><title>Effective Task Management in Small, Large and Multi-Team Development Environments</title><link>https://omid.dev/2024/05/31/effective-task-management-in-small-large-and-multi-team-development-environments/</link><pubDate>Fri, 31 May 2024 00:54:26 +0330</pubDate><guid>https://omid.dev/2024/05/31/effective-task-management-in-small-large-and-multi-team-development-environments/</guid><description>&lt;p&gt;In today&amp;rsquo;s fast-paced development landscape, effective task management is crucial for success. Whether you&amp;rsquo;re operating within a small team, a large organization, or a multi-team environment, managing tasks efficiently can make a significant difference in productivity, collaboration, and project outcomes. This blog post explores strategies for task management across different team sizes and structures, highlighting the roles of key personnel including CTOs, team leaders, and other common team members. We will also compare communication, flexibility, meetings, task allocation, monitoring, and challenges faced in these environments.&lt;/p&gt;</description></item><item><title>Essential Skills for a Frontend Team Leader</title><link>https://omid.dev/2024/05/24/essential-skills-for-a-frontend-team-leader/</link><pubDate>Fri, 24 May 2024 02:34:58 +0330</pubDate><guid>https://omid.dev/2024/05/24/essential-skills-for-a-frontend-team-leader/</guid><description>A named map of the frontend team-lead job — vision, delegation, feedback, tools, and how the week splits — plus the IC-to-lead shift and tech lead versus people lead.</description></item><item><title>Essential Skills for a Successful Senior Full-Stack Developer</title><link>https://omid.dev/2024/05/17/essential-skills-for-a-successful-senior-fullstack-developer/</link><pubDate>Fri, 17 May 2024 01:46:11 +0330</pubDate><guid>https://omid.dev/2024/05/17/essential-skills-for-a-successful-senior-fullstack-developer/</guid><description>A named map of the full-stack landscape for a frontend-shaped senior — languages, data, APIs, auth, and ops — and what changes when you own the contract, not just both folders.</description></item><item><title>Essential Skills for a Successful Senior Frontend Developer</title><link>https://omid.dev/2024/05/16/essential-skills-for-a-successful-senior-frontend-developer/</link><pubDate>Thu, 16 May 2024 18:42:26 +0330</pubDate><guid>https://omid.dev/2024/05/16/essential-skills-for-a-successful-senior-frontend-developer/</guid><description>A named map of the senior frontend landscape — language, framework, state, CSS, testing, delivery — and the judgment that separates owning a ticket from owning the outcome.</description></item></channel></rss>