Paving the Road to Effective Software Development
summary
Argues for a paved road platform that ships concrete outcomes: provisioning time drops from six months to ~15 minutes, microservices enable ~2,500 releases/month, and a container move cuts hosting costs ~40%. Builds: an internal platform with infrastructure-as-code, a change API that queues calls to avoid failures, BizOps graph with unique system codes and dashboards, automated DNS PR approvals, and a system operability score. Enforces guardrails but lets teams go off-road at higher support cost; patches log4j centrally.
AI-written summary · about
chapters (24)
- 0:00Intro
- 1:52Loosely coupled architectures
- 2:19Empowered teams
- 2:46Autonomy
- 5:16Paving the road
- 6:01Our path to the paved road
- 6:27Mandatory platform
- 9:13Financial Times platform
- 13:25Minimal platform
- 16:15Guardrails
- 23:23Paved road
- 29:56Principles for building paved roads
- 30:16Build what people need
- 32:55Reduce the risk of adopting it
- 33:59Don't make people wait
- 37:30Make things easy to use
- 38:51Allow people to extend & adapt
- 40:03Help people do the right thing
- 44:23Going off road
- 47:24The benefits of the paved road
- 47:41log4shell
- 49:46Wrapping up
- 51:07Principles for building the paved road
- 51:49Outro
related talks
54mDeveloper experience platforms
40mConstruction Time Again: A Lesson in Paving Paths for Security
38mBuilding a high quality product
46mWork It Smarter, Dev It Better, Ship It Faster, Test It Stronger
33mSoftware development practices for companies that want to make an impact
30m10 Ways to Improve How You Ship Software
26mSoftware Delivery from First Principles
37mPlatform Reality Has a Surprising Amount of Detail