Layering config without losing where a value came from
Four places a config value can come from, and the only question that matters at the wrong end of an incident: which one won, and why. Twenty minutes, one module, no services.
Tags
13 pages
Developer-Experience
Config is a border, not a chain
I built a boundary so I wouldn't have to move my config package. Then I moved it anyway, and the boundary is the only reason that didn't hurt.
Building it yourself is the third thing I try
I built somebody else's idea into a working skill before nine and deleted it by ten. Not-invented-here is the accusation; here's the order I actually work in.
Nine tags that were never on the branch
colophon works out the version your commits have earned, opens the release as a merge request, and tags what actually landed. Not what your forge says did.
A Slack channel with nobody in it
I asked nine agent sessions to stop compiling for forty minutes. What came back read like a team of colleagues, and I haven't worked out what to do about that.
Which one needs me next
A dozen agent sessions running at once is not a capacity problem. Working out which of them is stuck is, and the obvious way to find out is the wrong one.
Ready for human
I run a coding session per repository and they can't talk to each other. For a while the thing carrying messages between them was me, and I kept getting it wrong.
The grid that would not behave
A desktop-first photo tool reviewed mostly from a phone, and the CSS grid that refused to behave on the one screen it was being judged on.
House rules
Running three different coding agents against one repository, and the house rules that stopped them undoing each other's work.
A flag is not a setting
Reviewing a scaffolder turned up a command name that quietly conflated two different things. A flag and a setting are not the same object.
