Heyđ
Thanks for reading Exec Engineering, a weekly digest for the busy tech executive.
I hope this edition brings you value.
The Digest
Autonomy and Clarity in Leadership Styles (Bjorn Roche)
Bjorn Roche maps five leadership styles and when to use each. Autonomy works when problems decompose cleanly, Involvement works when you're the product expert, Policy works for repeated decisions like hiring, Conviction works when you have full context and need coordination, Consensus works when the decision requires more context than any one person has. The key is knowing which problem you're solving.
Building Software Organisations Where People Can Thrive (Ben Linders and Matthew Card / InfoQ)
The framework for thriving teams includes continuous learning (technical and soft skills), adaptability (space to experiment and recover), and support networks (outlets to connect and recharge). But the foundation is addressing toxic behavior, bias, and microaggressions immediately. Ignoring them quietly erodes the trust everything else depends on.
Making Engineers Autonomous (Aviv Ben-Yosef)
Leaders who canât delegate to their senior engineers wonât suddenly trust LLMs to write code. The bottleneck is you. Fix it by stopping the micromanagement flywheel: create guidelines instead of answering every question, clarify expectations about ownership and escalation, and give teams the context they need to spot shortcuts instead of waiting for instructions.
Creating momentum when an employee is stuck (Lara Hogan)
When someoneâs stuck in unproductive behavior, saying âstop doing Xâ triggers fight or flight. Instead, give them a âstart doing Yâ that serves your shared goal. Acknowledge their concern first so they feel heard, then redirect to the future. Save the blunt bottom line for when collaboration fails.
Things Iâve learned in my 10 years as an engineering manager (Joao Uchoa / Jampa.dev)
Best breakdown of what EMs should actually do: 10% doing technical work nobody else wants (not critical features that block your team), 30% coaching people to improve and preventing bad behaviors, 60% celebrating wins and making your engineersâ impact visible across the organization. Managers who code too much end up blocking their own teams.
âIf you canât take a month off and return to a well-functioning team, you need to work toward making that possible. Youâre too busy to be the bottleneck.â
Agentic IDEs - 100 Teenager Dev Problem (Subbu Allamaraju)
Managing AI coding tools is like managing 100 hyperactive teenagers who think they know everything. Theyâre fast, confident, and will happily break your architecture if youâre not watching. Instead of limiting them, Subbu says the best way to go about it is to build better guardrails through comprehensive tests, clear module boundaries, and automated workflows.
The 80% Problem in Agentic Coding (Addy Osmani / Elevate)
The winning pattern for AI coding is switching from telling agents how to code (step-by-step instructions) to telling them what success looks like (pass these tests, meet these requirements). Successful developers now spend most of their time defining problems clearly and verifying results, not writing code.
Influence, Power, and Product Management in Modern Product Companies (Shreyas Doshi)
When PMs complain they lack influence on product decisions, itâs usually a product sense or persuasion problem, not a power structure problem. Companies that hand PMs all the decision-making authority ship worse products over time. The best products come from cultures where engineers, designers, and PMs are equally invested in success, not where one function dominates the others.
Dialog
Eric Hoffert, CTO at Kargo, explains why taking innovative products to scale is less about moving faster and more about aligning technology with real user behavior.
In our latest Dialog, Eric breaks down how speed actually comes from focus, compact MVPs, and tight decision loops, why importing the wrong processes across company stages can quietly kill momentum, and how AI is reshaping engineering velocity when used as a force multiplier.
Check it out here:
More reads
Is the Internet Hijacking Our Ambition? (Cal Newport)
What makes for a âgreat place to workâ? (Make Work Better)
Sometimes Your Job is to Stay the Hell Out of the Way (Michael Lopp)
Making Space After Burnout (Jean Hsu)
10 Charts That Explain the AI Era (Deb Liu)
This digest is supported by Gemography.
Support your engineering team with remote high-ownership engineers from Africa and LatAm, on demand. Meet precise matches for your stack and culture under 48h.
About Exec Engineering
Iâm Yassine đ I spend a big chunk of my time digging into engineering management and talent acquisition, especially where the two overlap. I share the most interesting resources I come across in this newsletter, all curated by hand.






