The engineering manager's second architecture
A good manager shapes not just software architecture, but the operating architecture around a team.
19 published essays.
A good manager shapes not just software architecture, but the operating architecture around a team.
Engineers grow faster when managers give them meaningful responsibility, room to think, and enough support to learn from mistakes.
Staying hands-on as an engineering manager is not about control. It is about preserving technical judgment, credibility, and architectural clarity.
Public writing creates leverage far beyond personal expression. It sharpens judgment, attracts talent, and compounds credibility.
Small teams benefit from platform thinking earlier than they think, as long as they avoid platform theater.
A practical guide to using AI as an engineering manager without outsourcing judgment, coaching, or accountability.
How engineering managers can design 1:1s that create clarity, trust, and better decisions instead of repeating status.
Trust in distributed teams comes from predictability, clarity, and good written systems more than constant calls.
A practical view on engineering velocity metrics that improve decisions instead of incentivizing noise.
Delegation is not dumping tasks. It is the discipline of transferring ownership with enough clarity to create growth and speed.
Incident reviews should improve system behavior and team judgment, not just produce a document after a bad day.
Growing teams need better decision design, not just more meetings, approvals, and stakeholders.
Legal tech forces engineering teams to care deeply about precision, workflow design, trust, and usability under real business constraints.
Strong manager and staff engineer partnerships reduce noise, sharpen technical direction, and create healthier team execution.
Teams do not move faster by deleting every meeting. They move faster by making each one earn its place in the system.
Internal platform work earns trust when it removes friction clearly, ships visibly, and respects the realities of product teams.
The best runbooks reduce uncertainty during repeated work and incidents without becoming bloated process documents.
Skip-level meetings are valuable when they reveal patterns, risks, and context that the normal management chain cannot surface quickly enough.
Technical skills matter, but durable engineering careers are built on judgment about tradeoffs, systems, people, and timing.