/
3 min read
Feature Flags Solve Problems Until They Become the Problem
Flags are great for rollout safety. They are terrible as a long-term strategy for avoiding cleaner decisions.
Read article
Topic Hub
Web development
Opinionated articles on frameworks, rendering strategies, frontend complexity, performance tradeoffs, and building faster with less unnecessary machinery.
This category is where I push back hardest on web-development fashion. Most teams are not losing because they picked the wrong trendy stack. They’re losing because they added too much machinery before they earned the complexity.
Start with these:
- The 2026 Web Development Roadmap Nobody’s Saying Out Loud
- Why I Stopped Defaulting to React for Every Project
- Why I Build Everything With Astro Now (And Stopped Reaching for Next.js)
- HTMX Is Overkill (Until Your React Bundle Explodes)
- I Removed Sass From My Build Pipeline (And You Probably Should Too)
If you’re trying to simplify how you ship on the web, start here.
/
3 min read
Why So Many Internal Tools Become Permanent Accidents
Internal tools are supposed to be quick fixes. Then the business starts depending on them and nobody wants to admit a prototype became infrastructure.
Read article
/
14 min read
Rails Has Been Dying Since 2010. I'm Still Building Production On It in 2026.
Every couple of years someone publishes the Rails obituary. Every couple of years I ship another production system on it. The reason isn't loyalty — it's that nothing has actually replaced what Rails decided to do.
Read article
/
4 min read
The Best Stack Is the One Your Team Can Debug at 2 A.M.
Stack decisions are not just about developer experience on launch day. They are about who can understand the failure when production gets weird.
Read article
/
4 min read
Most API Versioning Advice Falls Apart in the Real World
The argument is rarely about URLs versus headers. The real problem is that most teams version without a consumer strategy, a deprecation plan, or any operational discipline.
Read article
/
4 min read
Most Teams Do Not Need Microservices. They Need Better Boundaries.
Splitting a messy system into five deployables does not create clarity. It usually creates more places for the same confusion to hide.
Read article