Blog

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. read more >

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… read more >

Most companies organize customer tools around their own org chart, then wonder why customers get frustrated. The structure that makes internal work easier is usually the one that makes customer problems harder to solve. read more >

Exploring how small steps create invisible friction that stops us from getting things done, and why eliminating decisions matters more than saving time. read more >

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. read more >

The smoothest systems aren’t always the best ones. Sometimes the pause, the confirmation dialog, the friction that makes you slow down—that’s not poor design. That’s the system being honest about what’s actually happening.

I watched someone try to register their device three times before it worked. Each time, the system asked: Are you sure? Is this the right account? Should we send a confirmation code?

It felt annoying. Then I realized: those pauses prevented a mistake that would have locked them out completely.

Most knowledge work never finishes. It just stops. The start, ship, close, and sum-up methodology creates deliberate moments that turn continuous work into resolved units. read more >

The hardest part of documentation isn’t writing it. It’s making sure the right people actually see it. You can write brilliant work logs explaining decisions and tradeoffs, but if they live in a work-log directory that nobody remembers to check, they might as well not exist. The information has to flow to where people already are - Slack channels, Discord servers, project management tools, email inboxes.

This is about building a system that broadcasts work logs across multiple destinations automatically, with graceful degradation and per-project routing. But really it’s about …

The tools you build determine what kinds of thinking become possible. On infrastructure, friction, and building deliberately for thought rather than just throughput. read more >

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. read more >