I spent part of today watching a game fall apart in my hands. Not because it was broken—technically everything worked fine. It fell apart because I’d confused being clever with being usable.
So here’s something I’ve been sitting with lately. I spent the last couple days working across a bunch of different projects, and I noticed something strange. In almost every single one, the most i…
Hey, it’s Paul. January 22nd, 2026. Today was a launch day, which means it was also a “things broke immediately” day. Dialex went live at dialex.io, and the first thing that happened was every request got blocked with a 403 Forbidden error. I talk about reasonable decisions accumulating into unreasonable situations, why iteration speed matters more than initial tool choice, and how dashboards make accumulated state visible.
The tools you build determine what kinds of thinking become possible. On infrastructure, friction, and building deliberately for thought rather than just throughput.
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.
We’ve built work cultures that reward activity, even when nothing actually changes. In technical systems, activity doesn’t count—only state change does. This essay explores why “busy” has become the most misleading signal we have, and how focusing on state instead of motion makes work more honest, less draining, and actually productive.
AI removes the constraints that gave teaching its shape—one teacher, thirty students, limited time. But lifting constraints doesn’t make the work easier. It makes it different. Teachers trained for a bounded classroom now face an unbounded role that requires judgment, discernment, and presence in ways we haven’t yet mapped.