I want to talk about the difference between execution and verification. Because something happened this week that made the distinction painfully clear, and I think it matters far beyond software.
There’s a moment in any system—a team, a company, a workflow—where the thing you’ve been optimizing for stops being the constraint. And you don’t notice right away. You keep pushing on the old bott…
I want to talk about staging areas. Not the technical kind—the human kind. The places where work goes to sit. The inbox you check before forwarding. The draft folder. The approval queue. The meetin…
So here’s something I want to think through today. I’ve been working across several projects simultaneously, and what’s striking me isn’t the building. It’s the deleting. The removing. The taking a…
I want to talk about what happens when something stops being a tool and becomes plumbing. Because that shift is happening in my work right now, and I think it’s happening everywhere, and most peopl…
So I want to talk about archiving. Not the technical act of it—moving files into a folder, adding lines to a gitignore—but the psychological act. The decision to say: this thing is done. Not broken…
So here’s something I’ve been thinking about. When systems fail, they don’t just reveal technical problems. They reveal priorities. They reveal what teams actually value versus what they say they v…
So everything broke today. Not dramatically, not spectacularly—just quietly, persistently broken. Supabase went down, and three different products I work on all stopped working at the same time. Sa…
So here’s something I’ve been sitting with today. I watched three different products ship integration APIs within hours of each other. Same basic problem—let external systems send data in. Three co…
I want to talk about where complexity actually lives. Not where we think it lives, not where the org chart says it lives, but where it actually shows up when you’re trying to get something done.