Opening the books: an engineering diary for The Dugout

Most of the interesting decisions I've made building The Dugout only exist as commit messages and pull request summaries, which is another way of saying they don't really exist. Nobody opens a squashed merge commit and comes away knowing why the standings query looks the way it does, or why an idea that seemed obvious on a Tuesday was dead by Thursday.

So: a diary.

Not release notes for managers — those come later, and when they come they should read like release notes. This is the other thing. Which systems earned permanence and which attractive ideas stayed sketches. The dead ends. The weeks where the right answer turned out to be several answers instead of one.

It'll mostly be about the product and the loops a manager actually lives in: match day, seasons, transfers, staff, youth. Security work, admin tooling and the operational side get a mention at the surface and nothing more — partly because this is a public page, and partly because nobody needs my runbooks.

That's it. The posts start where the work did.