I have "Code Brain"
Paul Krugman outlined the economics of "Car Brain" in his recent article about the congestion economics of cars, commuters, and the city of New Year. That concept resonated in a huge way!
We need to refactor again!
This is the battle cry of many developers when faced with technology changes, recurring bugs, or scaling issues.
End-of-Day Revenue
Everyone understands revenue. That’s why I use it as a forcing function. If it doesn’t earn value today, it’s not worth your weekend.
The Sunk Cost Illusion
Founders often mistake early code for progress. But the real challenge isn’t shipping features — it’s avoiding the trap of sunk cost thinking. This post breaks down why pausing before you commit is the smartest move you can make.
Why Developers Always Want to Build — and How It Costs Us
Every time I asked my team to evaluate SaaS tools, I watched the same thing happen. A predictable resistance. A build-first mindset. And over time, I realized: it wasn’t just bias — it was culture.
Latest Posts
AI Adoption Patterns
I am a developer. While I have no intention of going back to being a staff engineer, wrangling code, branches, PRs, and agile process, I do rely on my background to get things moving. Engineering rigor is the pattern. AI adoption in the tech community has some things to teach (to me).
Typeform: What happened?
Forms used to feel like progress. Typeform was sleek, Google Forms was simple, and building your own meant control. But today, AI agents are rewriting the rules. They gather data with context, tone, and flow—no rigid input fields required. Going back to old-school forms feels like switching from Spotify to a cassette tape. The tools didn’t just age—they missed the AI shift.
Post Vibe Coding
It seems like a long time ago that I decided to try a No-Code February. Going cold turkey on code has some interesting side effects. The math of applying AI coding tools to advising and consulting has forced some changes in how I approach all code projects: Launch By Lunch AI Accelerators, Vibe Coding Office Hours, and tech stack audits. And a renewed focus on the scoring site of the low-code cookbook.
