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.
Nobody takes you aside anymore
Print taught a generation when to stop. What we lose when the machines absorb the constraints that used to form us.
Your AI agents need a water cooler
Coordination is a property of the room, not the org chart. What that means when your coworkers are agents.
On the death of the author and the birth of the detector
Why worrying about AI authorship is lazier, and more prejudiced, than it looks.
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.
Memory is (almost) solved. time is next.
AI can't tell if a memory is two minutes or two weeks old. The fix isn't making models feel time — it's cache invalidation: an as-of stamp on every fact, a clock in the context, and a freshness window for anything volatile.
Did the state change? A simple test for whether work actually happened
Either something exists now that did not exist before, or it does not. A simple test for whether work actually happened, and what changes when you build your systems so they can't record anything else.
How to manage content for multiple clients without flattening their voices
How to manage content for multiple clients without their voices blurring into one house style: a workspace and a voice profile per client, batchable stages, and approval buffers.
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.