Tagged microservices
-
The Biggest Problem With Our Codebase Is the Developers
Or: What Platform Teams Actually Exist For (And Why Most Get It Completely Backwards)
-
Your New System Is Done. Now Good Luck Getting 40 Teams to Care.
Or: What Nobody Tells You About Retiring a Legacy System
-
Stop Copying Prod Into Dev: Test Data Strategies That Actually Scale
Or: Your Database Snapshots Are a Confession, Not a Solution
-
The Lego Problem: Why Engineers Add Complexity Instead of Removing It
Or: Why Your Architecture Reviews Have a Benefit Slide and No Cost Slide
-
Designing APIs That Outlive Your Current Sprint
Or: Why Your API Contract Is the Most Important Code You’ll Never Unit Test
-
Show Me the Architecture and I’ll Show You the Silos
Or: How We Broke Down Our Monolith and Accidentally Built Walls Between Our Teams
-
Resilience Isn’t a Feature — It’s the Absence of Naivety
Or: Why Your System Is One Slow Query Away from a Very Bad Night
-
Centralization Is Contention: The Hidden Tax on Your Engineering Velocity
Or: Why Every Centralized Team Becomes a Bottleneck (And the Math to Prove It)
-
The 40-Minute Pipeline: Why Your Build System Is Making You Dumber
Or: How We Measured What Everyone Suspects But Nobody Wants to Talk About
-
Semantic Monitoring: The Question You’re Not Asking About Your Production Systems
Or: Why Your Dashboards Are Green and Your Business Is Bleeding
-
The Tangled Web We Weave: How Moving Fast Led Us Down the Synchronous Coupling Rabbit Hole
“The chains of habit are too weak to be felt until they are too strong to be broken.” — Warren Buffett