The revised rules of engineering management with Will Larson

The podcast discusses the evolving role of software engineers and engineering leadership in response to technological and economic shifts. It highlights how the era of zero interest rates influenced management practices, leading to bloated teams and misaligned incentives, while the rise of AI is now transforming engineering workflows, reducing the need for manual coding, and increasing focus on strategic decision-making. The discussion emphasizes that solving business-critical problems has become essential for career advancement, and traditional career ladders are being challenged as AI takes over routine tasks.

Further exploration includes the changing path to executive roles, with line managers increasingly seen as better equipped for CTO positions than middle managers, who often lack deep technical engagement. The conversation covers the decline of middle management, the importance of durable, high-ownership teams, and the need for engineers to develop business acumen. It also examines the value of writing in shaping industry practices, the risks of AI-generated content diluting authentic voices, and the importance of quality over quantity in thought leadership. The overall narrative reflects a profession in transition, requiring adaptability, hands-on involvement, and a rethinking of traditional structures.

• What if you focused your solo software business on solving one business-critical problem instead of chasing feature velocity?

  • Move: Identify a high-impact, under-served business process (e.g., contract renewal leakage, user onboarding drop-off) in your target market and build a micro-SaaS tool around it.
  • Why Now?: AI reduces coding effort, making it feasible to deliver deep business value with minimal code - shifting competitive advantage from output to problem selection.
  • Expected Upside: Higher pricing power, faster sales cycles, and defensibility through domain-specific insight rather than generic features.

• What if you replaced traditional code reviews with automated hostile testing to catch bugs before users do?

  • Move: Integrate a tool like Antisys into your CI/CD pipeline to run deterministic, adversarial simulations on every PR, especially for AI-generated code.
  • Why Now?: As AI agents produce more code, human review becomes a bottleneck; automated stress testing ensures reliability without slowing velocity.
  • Expected Upside: Fewer production incidents, faster iteration, and increased confidence in AI-assisted development - critical for solo operators with no QA team.

• What if you operated as a durable, high-ownership team of one - applying pod-style autonomy to your solo workflow?

  • Move: Structure your work like a self-contained team: own a narrow domain (e.g., billing infrastructure), define clear outputs, and minimize context switching by batching communication and tasks.
  • Why Now?: The industry shift toward smaller, outcome-driven teams favors solo operators who can emulate high-performing pods without overhead.
  • Expected Upside: Faster decision-making, deeper domain mastery, and higher throughput - mimicking the effectiveness of elite engineering teams at scale.

• Audit and document your current software system's critical paths and failure points, then build lightweight monitoring or caching solutions (e.g., using Redis) to stabilize performance during transitions.
• Focus your technical work on solving direct business-critical problems - even if unglamorous - to increase career leverage and alignment with organizational survival needs.
• Write and publish concise, authentic technical content based on real projects or decisions, prioritizing clarity and impact over volume to build long-term credibility and influence.
• Reevaluate team structure assumptions: maintain small, durable, high-ownership teams instead of scaling headcount, to preserve productivity and avoid coordination debt.
• Proactively reskill by taking lateral or smaller-scope technical roles if needed, especially after periods of management or bureaucracy, to stay hands-on and adaptable in a changing engineering landscape.