What systems can't fix
I’m a systems person. The work I’m proudest of is the kind nobody notices: the test suite that catches the bug before review, the pipeline that makes the safe path the easy path, the process that quietly turns the right thing into the default. Get it right and the improvement compounds. You fix something once and it stays fixed, long after you’ve moved on. That instinct has served me well. When a team is slow and chaotic, the fix is usually structural. At one company we took release cycles from three or four months down to two weeks, not by asking people to try harder but by moving to trunk-based development, wiring up CI, and putting real quality gates in the path. The system became automatic. It was the default. People did the right thing because the right thing was the easy thing. ...