Field notes on building software that holds up.
What separates a build that ships well from one that gets quietly rebuilt by the next team sixteen weeks later. Written for the founders deciding what to build, who to hire, and whether the dev team in front of them knows the difference.
The New Software Economics: Cheap Code, Expensive Attention
Code is no longer the moat. As AI collapses the cost of building, the scarce resource shifts to attention earned through solving meaningful problems.
AI Can Write the Code. It Still Can't Tell You What to Build.
The risk in 2026 isn't that AI can't write code. It's that we are writing code faster than we can think. Why translation, system design, and precision are the new premiums.
The Difference Between Working Software and Production Software
Every developer tests their own code like it's made of blown glass. QA testers bring a sledgehammer. That relationship is the only thing standing between your app and a Friday night production crisis.
Building an App People Actually Use is an Art
Three mental models for building something people actually open: bucket of water, pitcher plant, and why the MVP is dead.
Hiring an App Developer? Two Questions Every Founder Should Ask First
Two diagnostic questions cut through every dev shop pitch. Most app builds fail because the founder picked a team that could ship code but could not engineer software.
Vibe Coding 16 Weeks Later: The Hidden Cost of Building Software on AI Vibes
Vibe coding looks like a 20-minute adventure on day one. By week 16 you are paying a different team to rebuild it.
Working Code Isn't Production-Ready Code: What AI Misses When It Writes Software
AI can generate code that runs without errors. That is not the same as code that survives contact with real users.
Have a build in front of you?
A roadmap call walks through what you're trying to build, what's already there, and what we'd recommend. No charge for the first conversation.