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.
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.
The case for corporate amnesia
Most organizations worship institutional memory. But what if the thing they're preserving is mostly decay?
Your design philosophy is already written
Builders who work across multiple projects leave fingerprints everywhere. The same mind solves the same problem differently in every domain — and usually doesn't notice. You need someone to read it back to you.
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.
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.