/
3 min read
Background Jobs Are Where Web Apps Go to Hide Complexity
Teams love pushing work into the background because the request gets faster. They forget the complexity did not disappear. It just moved somewhere less visible.
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
Shared Component Libraries Break Faster Than Teams Admit
A design system can reduce duplication, but teams keep turning shared component libraries into cross-team bottlenecks that slow everyone down.
Read article
/
3 min read
The Migration That Works in Dev and Locks Production
Schema changes look safe in tiny local databases. Production is where table size, lock time, and rollout order turn an ordinary migration into a real incident.
Read article
/
3 min read
Your Uptime Dashboard Is Not Measuring User Experience
A service can be technically "up" while users are getting timeouts, stale data, and broken workflows. Teams that monitor availability alone miss the pain customers actually feel.
Read article
/
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