Reading path

Engineering Leadership

A curated reading path for leads and architects — essential skills, soft skills, and essays on teams and architecture.

For tech leads, architects, and senior engineers who want practical guidance on skills, communication, and the judgment calls that shape teams — beyond pure technical depth.

Essential skills

Pick the guide that matches your role — each stands alone, or follow the Essential Skills series in order:

  1. Essential Skills for a Senior Frontend Developer — Outcomes over tool lists: the IC craft bar that separates a senior from a strong mid.
  2. Essential Skills for a Senior Full-Stack Developer — What changes when a frontend-shaped senior owns the other side of the contract.
  3. Essential Skills for a Frontend Team Leader — The IC-to-lead shift, tech lead versus people lead, and how the week actually splits.
  4. Essential Skills When Generation Is Cheap — Own output you did not type, review at working-but-wrong, and decide where generation does not belong.

Soft skills cluster

Follow the Team Communication series:

  1. Conflict Resolution in Tech Teams — Mediation techniques when technical disagreements become personal.
  2. Effective Communication for Developers — Bridging technical and non-technical stakeholders without dumbing down the work.
  3. Effective Task Management — Task systems that scale from one team to many.

Shadow ownership

Follow the Shadow Ownership series in order, or use the in-post navigation:

  1. When the Best Communicator Becomes the Backdoor — Diagnose when valuable cross-team influence turns into unofficial ownership.
  2. Channel the Scout, Keep the Seat — A lead’s playbook for visible intake, bounded commitments, and polish on a budget.
  3. Have Influence Without Becoming the Backdoor — A senior developer’s guide to protecting users without becoming the shadow owner.

Team building and judgment

  1. Building Resilient Teams — Practices for teams that recover from setbacks and ship under pressure.
  2. Mentorship in Tech — How to mentor and be mentored without performative coaching.
  3. I Interview Frontend Hires for Other Companies — Hiring for a team that is not yours: intake, choosing the real level, and a loop that refuses the false yes.
  4. Choosing the Right Tech Stack — Framework for architecture decisions that outlive the hype cycle.

Ecosystem blind spot

Follow the Ecosystem Blind Spot series in order, or use the in-post navigation:

  1. The Zoom-Out: Ecosystem Blind Spot — When 15 years of depth meets the tooling you never had time to learn.
  2. After the Zoom-Out: A Playbook for Staying Current — Pain-driven discovery, pattern recognition, and quarterly reconnaissance without the shame spiral.

Essays and architecture judgment

  1. The Cost of Consistency: Design System Bottlenecks — Lessons from building a design system without the rigidity trap.
  2. The Engineer’s Dilemma: Startup Execution — When you want to build products, not just write code.
  3. The Frontend Is a Privileged System Now — Frontend delivery accumulates production authority; architecture includes CI identities, not just the component tree.

Modernization judgment

  1. Legacy and Modernization — Code archaeology and the ethics of rewriting (2-post series).