Opinion
Choose Boring Technology, Except Where It Matters
The advice is right and incomplete. The interesting question is where to spend your limited budget for novelty.
Debugging
Recovering Work After a Bad git reset --hard
Your commits are almost certainly still there. Here is how reflog works, what it cannot save, and the recovery path for each case.
AI
Testing an LLM Feature When the Output Is Different Every Time
You cannot assert equality on a model response. You can assert a lot of other things, and most teams assert none of them.
Debugging
What Running Hosting Infrastructure Taught Me About Debugging
Five years of keeping other people's websites online rewired how I think about failure. Mostly by making the consequences immediate.
Debugging
Every Bug Is a Story About a Wrong Assumption
Why I started a blog about software failure instead of software success, and what a debugging writeup should actually contain.
DevOps
Structured Logging, and What to Actually Put in a Log Line
Most logs are unqueryable prose written for a human who will never read them. Here is what makes a log line useful during an incident.
DevOps
Three Metrics That Would Have Caught Most of My Production Incidents
Not a guide to observability platforms. Just the three signals that, in retrospect, would have given me warning before nearly everything that went wrong.
AI
How to Review a 900 Line AI Pull Request Without Losing Your Mind
Large diffs used to signal that somebody worked hard. Now they signal that a prompt was short. Review has to change shape.
AI
Writing an AGENTS.md That Actually Reduces Bugs
Most agent instruction files are a list of vibes. Here is what belongs in one, based on which rules measurably changed the output.
Debugging
Your Flaky Tests Are Not Flaky, They Are Telling You Something
A test that fails one time in fifty is reporting a real property of your system. Retrying it is throwing away the evidence.