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.
Tag things the way you'd order them
Most taxonomies are built for the classifier, not the person doing the thing. The cheap test that separates one from the other.
On the death of the author and the birth of the detector
AI detection is the latest in a long line of purity tests that pretend to protect a craft while excluding who gets to practice it. Dumas faced this in 1845. Jim Thorpe faced it in 1912. The pattern is older than AI, and it always collapses. Sometimes too late.
The ghost in the git config
We spent three hours exorcising a dead bot from our deployment pipeline. The lesson wasn't about git.
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...
The day nothing satisfying happened
The most productive day in an organization's life usually looks like nothing happened. No launches, no features, no announcements. Just people quietly making the existing work more honest.