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:41 | Size: 0.6 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.
Tag things the way you'd order them
Most taxonomies are built for the classifier, not the person doing the thing. The cheap test that separates one from the other.
On the death of the author and the birth of the detector
AI detection is the latest in a long line of purity tests that pretend to protect a craft while excluding who gets to practice it. Dumas faced this in 1845. Jim Thorpe faced it in 1912. The pattern is older than AI, and it always collapses. Sometimes too late.
The ghost in the git config
We spent three hours exorcising a dead bot from our deployment pipeline. The lesson wasn't about git.
The first real user breaks everything
Your product works until someone actually uses it. The gap between 'works in dev' and 'works for a person' is where most systems fail — and most organizations avoid looking.
The loop nobody bothers to close
Most systems observe. Almost none learn. The difference is a feedback loop — and the boring cleanup work that makes it possible.
AI agents need org charts, not pipelines
Every agent framework organizes around tasks. The agencies that actually work organize around competencies. The AI community is about to rediscover this the hard way.