Opinion
Every runbook I have ever opened during an incident was wrong. Not catastrophically, not uselessly, but wrong in the specific way that costs fifteen minutes at three in the morning: the dashboard had been renamed, the command needed a flag that did not exist when it was written, and the
MicroVMs
The question is not whether an autonomous agent will do something destructive. It is what the destruction can reach when it does.
Opinion
Positions I argued for, sometimes loudly, that turned out to be mistaken. What changed my mind in each case.
Debugging
An error message is read by a person under stress who needs to make a decision. Almost nobody designs them that way.
Engineering Culture
A document nobody reads, listing action items nobody does, produced to satisfy a process. Here is the version that actually changes something.
Shopify
Headless Shopify is genuinely better for some stores and a costly mistake for most. Here is how to tell which one you are.
Debugging
Every layer you add to avoid repetition adds a place where the truth can hide. Here is how to tell which abstractions earn their cost.
Debugging
Using a debugger is supposedly the mark of a serious engineer. Print statements are supposedly what beginners do. Both of those claims are wrong.
Engineering Culture
They are genuinely useful and every one you leave in place multiplies the number of code paths nobody tests. Here is how to keep the benefit.
AI
Every mitigation at the model layer can be worked around. The fix is architectural: assume the model will be compromised and limit what it can do.
Shopify
I build Shopify themes for a living, which makes me exactly the wrong person to ask and exactly the right person to ask. Here is where each platform actually wins.
Opinion
The advice is right and incomplete. The interesting question is where to spend your limited budget for novelty.