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:

If you’re trying to simplify how you ship on the web, start here.

/ 4 min read

Your Logging Strategy Is Not Observability

Dumping more lines into a log platform does not mean your team can understand a failure under pressure. Most logging strategies only create noisier confusion.

Read article
/ 3 min read

The Backend Is Not Boring. It Is Where Bad Decisions Get Expensive.

Frontend trends change every year. Backend mistakes keep charging interest long after the UI refresh ships.

Read article
/ 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
/ 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