
False Speed
If you measure speed up to the deploy and leave out what happens after, you can present work pushed into the future as an improvement.
I write about code, design, technology, and whatever else steals my attention. Most older posts started in Spanish; both versions now live side by side.

If you measure speed up to the deploy and leave out what happens after, you can present work pushed into the future as an improvement.

Being able to automate something doesn't mean you should. Before you speed up a task, understand what limits the whole process.

AI can explain what a system does, but not why we decided to build it that way. Why ADRs are still worth writing, even if they're three paragraphs long.

A green deploy doesn't tell you whether your AI gave a good answer. How a quiet failure in a side project taught me what evals are for, and why the first step is reading.

AI can help us deliver work without building, to the same degree, the judgment to understand it. What that means for people starting out and for the teams that should be training them.

Conway said in 1968 that software copies how the organization that builds it communicates. What does it copy when everyone mostly talks to an AI?

In his Rails World 2026 keynote, DHH said 37signals no longer writes code by hand and that HEY is being rebuilt without Rails. What he actually said, what he didn't, and why the whole talk is worth your time.

Behind a pension calculator there is a person with a much simpler question: how much money will I have to live on when I retire? On designing from that question rather than from how the system works, and why AI should let users understand less, not more.

The narrative of abandoning projects and organizing around products won, and it was right about almost everything. But several organizations confused eliminating the project manager with eliminating their responsibilities. About a job that was left without an explicit owner.
39 more articles, since 2013.