When intelligence gets cheap, judgment becomes priceless
A lot of people are treating AI like it's going to replace "thinking." It won't. What it will replace is the comforting illusion that thinking was...
A lot of people are treating AI like it’s going to replace “thinking.” It won’t.
What it will replace is the comforting illusion that thinking was optional.
AI is great at producing an answer. It’s terrible at taking responsibility for one.
It can generate a strategy, a lesson plan, a policy, a diagnosis. But it can’t own the consequences when the strategy fails, the lesson lands wrong, the policy harms someone, the diagnosis is incomplete.
That part is still on us.
So the question is not “how do I compete with AI?” The question is “what kind of human am I willing to be when I can’t hide behind the task anymore?”
When intelligence gets cheap, judgment becomes priceless.
That’s the work.
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.
Manual fluency is the prerequisite for agent supervision
You cannot responsibly automate what you cannot do manually. AI agents speed up work for people who already know how to do it. They do not replace the need to learn the work in the first place.
The gun you didn't need
Every organization has loaded weapons lying around that nobody remembers loading. The most dangerous capability in any system is the one you built 'just in case.'
Nobody promotes you to operator
There's a moment in every project where the work stops being about building and starts being about keeping things running. Nobody announces this transition. Nobody gives you new tools for it. And most people keep building long past the point where they should have stopped.
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.
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...
Nothing is finished until you say it is
Continuous delivery removed the endings from work. That felt like progress. But without formal completion, you lose the ability to say what you actually accomplished — and more importantly, what you're done thinking about.