Build for the loop, not the lecture
A junior developer used to wait days for mentor feedback. Now that loop closes in seconds. When feedback is scarce, you batch your questions. When feedback is abundant, learning becomes continuous. AI changes the supply side of learning—most of our systems weren't designed for this.
Duration: 0:38 | Size: 0.59 MB
A junior developer used to wait days for mentor feedback. Now that loop closes in seconds. This is not a small change.
When feedback is scarce, you batch your questions. You guess. You move on and hope. The gaps between learning moments stretch long. Mistakes harden into habits before anyone notices.
When feedback is abundant, learning becomes continuous. Small corrections compound. The rhythm shifts from episodic to constant.
We designed most learning systems around scarcity. Scarce experts. Scarce attention. Scarce time. AI changes the supply side.
The harder question is whether we’ll design for abundance or keep rationing what’s no longer scarce.
Build for the loop, not the lecture.
Why customer tools are organized wrong
This article reveals a fundamental flaw in how customer support tools are designed—organizing by interaction type instead of by customer—and explains why this fragmentation wastes time and obscures the full picture you need to help users effectively.
Infrastructure shapes thought
The tools you build determine what kinds of thinking become possible. On infrastructure, friction, and building deliberately for thought rather than just throughput.
Server-side dashboard architecture: Why moving data fetching off the browser changes everything
How choosing server-side rendering solved security, CORS, and credential management problems I didn't know I had.
The work of being available now
A book on AI, judgment, and staying human at work.
The practice of work in progress
Practical essays on how work actually gets done.
Nothing is finished until you say it is
Continuous delivery removed the endings from work. That felt like progress. But without formal completion, you lose the ability to say what you actually accomplished — and more importantly, what you're done thinking about.
Your biggest problems are the ones running fine
The most dangerous failures in any system — technical or organizational — aren't the ones throwing errors. They're the ones that appear to work perfectly. And they'll keep appearing to work perfectly right up until they don't.
The work that remains
When AI handles implementation, the human job shifts from doing the work to understanding the work. Speed without understanding is just technical debt with better commit messages.
If it can be automated, it wasn’t the work
I keep noticing people talk about AI like it's a wave that's about to hit them. "Will it take my job?" "How do we adopt it fast enough?" "How do we...
When intelligence gets cheap, judgment becomes priceless
A lot of people are treating AI like it's going to replace "thinking." It won't. What it will replace is the comforting illusion that thinking was...
Nothing is finished until you say it is
Continuous delivery removed the endings from work. That felt like progress. But without formal completion, you lose the ability to say what you actually accomplished — and more importantly, what you're done thinking about.