A Plea for Boring Tech
summary
Argues that production systems use the most boring reliable tech so teams spend time building features not fighting the stack, citing costly rewrites, pagerduty-driven outages and information bottlenecks when one or two people own a new stack. Gives a concrete win: 30+ teams at IBM successfully adopt GraphQL after heavy work and interop payoff. Proposes a risk checklist with CHAOS: complex hazardous aspirational opaque speculative and recommends assessing retraining, infra, ownership and real user value before introducing novelty.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:12Two Wolves at Battle
- 2:58Boring is for Builders
- 5:59Embrace Chaos
- 12:42Types of Excitement
- 13:52The Hard Way
- 15:10Sides of Shipping
- 17:20Balance
- 18:26Risk Assessment
- 18:50Outreach
related talks
26mBe Awesome By Being Boring
43mBuild “boring” engineering orgs
01h 13mThe most boring decision: how to choose technologies when you're no longer a startup
55mShiny objects are cool, but so is building products people use
39mStop Focusing on Tech Debt
30mEngineering in Overdrive: How to Thrive When Tech Evolution Goes Full Gas
02mA young lady's illustrated primer to technical decision making
09mInterview with