If it can be automated, it wasn't the work
I keep noticing people talk about AI like it’s a wave that’s about to hit them.
“Will it take my job?” “How do we adopt it fast enough?” “How do we protect ourselves?”
Those are understandable questions. They’re also a little late. If AI can do your job, the problem isn’t the AI. The problem is that your job was never designed to require the human part of you.
Most organizations have spent decades trying to remove judgment from work. Scripts. Processes. Compliance. “Just follow the playbook.” It worked because humans are adaptable. We learned to shrink.
Now the machines showed up. And they’re better at machine-work than we ever were.
Rule: if the work can be automated end-to-end, it wasn’t the work.
The work is what’s left. That’s the human era.
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.
Dev reflection - February 17, 2026
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...
Dev reflection - February 16, 2026
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...
Dev reflection - February 15, 2026
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...
You were trained to suppress yourself
Organizations didn't accidentally reward the machine-self. They engineered it. And you cooperated because it worked—until now.
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.