You finish a feature and you’re holding a hook, a helper, a type, and a stylesheet. Where do they go? For a while our answer was “it depends,” which is another way of saying nobody knew.

This is how we settled on one folder per feature, and how we stopped it from drifting back into a mess.

Three AI coding tools, three config files, all slowly disagreeing with each other and with the code. This is how we got down to one source of truth the robots and the humans both read.

A React app crashes. Sentry tells you it crashed. It does not tell you whose crash it is. You can usually work that out. It’s just a step nobody should have to do by hand.

This is the story of how we taught our error boundaries to tag the team that owns the screen, so the report answers that question on its own.

The promotion earns you the title. It does not teach you the job.

In March 2026 we ran Tech Lead School, an honest attempt to close the gap between what earns the promotion and what the role actually demands. Here is what worked, what didn’t, and what surprised us.

Our hiring process was not broken in an obvious way. It produced reasonable outcomes and we had learned to live with its inefficiencies. But over time the cost of running it became impossible to justify. I could have looked the other way. But I have always believed in leaving the battlefield better than I found it. This is the story of how we identified its shortcomings, redesigned the process around our actual constraints, and handed ownership of it to the entire team.

Senior engineering management is mostly subtraction. The brief you don’t over-specify. The standard you don’t leave verbal. The conversation you don’t have because the team is already having it.

But subtraction is not absence. It only works when the infrastructure underneath is honest: a clear end state, written standards, accountability that survives your calendar, and protection from the org above. This is the version of the job I’ve been learning the hard way.