Paving the Road to Effective Software Development
summary
Describes how a Financial Times engineering enablement group builds a paved road platform that cuts provisioning from six months to minutes and raises deployments to ~100 releases a day, while keeping autonomy via documented guardrails. Explains concrete tooling: a graph database of systems and owners, a change API with a CircleCI orb, runbook scoring and automated DNS PR approvals. Shows what teams must do to go off‑road, how costs and security are controlled, and that the approach succeeds in practice.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:49Loosely coupled architectures
- 2:25Empowered teams
- 2:45Autonomy
- 5:15Paving the road
- 5:50Our path to the paved road
- 8:05Financial Times platform
- 12:06Minimal platform
- 14:35Guardrails
- 19:32Paved road
- 25:28Principles for building paved roads
- 26:08Build what people need
- 29:01Reduce the risk of adopting it
- 30:07Don't make people wait
- 33:31Make things easy to use
- 34:06Allow people to extend & adapt
- 36:03Help people do the right thing
- 39:32Going off road
- 41:18log4shell
- 42:02Wrapping up
- 43:21Principles for building the paved road
- 43:57Outro
related talks
33mPaving the Road to Effective Software Development
40mPractices from trenches for embracing evolutionary architecture in wild
11mLeading without committing: Managing teams outside your tech stack
46mMaster Software Architecture: From Simplicity to Complexity
56mThe Nature of Software Development
44mAvoiding the pitfalls of rebuilding software
57mHow the right tools help deploy the right architecture
26mFrom friction to function: Strengthening the product-engineering alliance