Building in public is broken — Here’s how to fix your signal-to-noise ratio
Building in public promised accountability and community. It delivered content production under a different name. Most builders now spend more time documenting work than doing it, trapped in a perform
Building in public promised accountability and community. It delivered content production under a different name. Most builders now spend more time documenting work than doing it, trapped in a performance loop that optimizes for platforms instead of progress.
The agent-shaped org chart
Every real org has the same topology: principal, role-holder, specialists. Staff AI maps onto it, node for node, and the cost collapse shows up in the deliverables that were always just human-handoff overhead.
AI as staff, not software
Two frames for what AI is doing to work. The tool frame makes tools smarter. The staff frame makes roles unnecessary. Those aren't the same product, the same company, or the same industry.
Knowledge work was never work
Knowledge work was always coordination between humans who couldn't share state directly. The artifacts were never the work. They were the overhead — and AI just made the overhead optional.
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.
How do I get my dev team to adopt AI?
A stub on helping mixed-interest development teams find their own useful ways into AI.
Want to learn about agents? Talk to someone who ran an agency.
I spent 20 years running consulting engagements at Fortune 500 companies. Turns out that's the best preparation for running a fleet of AI agents ... because the problems are identical.
Your AI agents need a water cooler
We run a twelve-session AI fleet that coordinates through an IRC breakroom. A friend asked: why are you making AI agents act like humans? The answer turned out to be more interesting than the question.
Why your thought leadership content pipeline is broken
The problem isn't workflow efficiency. It's that you're treating thought leadership like a manufacturing process when it's actually a translation problem.
The intelligence briefing you’re not getting
Most knowledge workers spend 45 to 90 minutes each morning manually triaging the internet. The time already exists in your day. You're just spending it on filtering instead of reading.