Sustaining Engineering - life after devops?
summary
Argues for a persistent sustaining engineering team that takes ownership of live services and handles incidents, long-term architecture, backups, DR, instance resizing, and deployment‑time creep rather than one‑off firefighting. Proposes a staffed mix of junior and experienced engineers, a catalogue of supported services, automation and defaults for monitoring and tooling, and transition patterns labeled lighthouses dogs puppies. Targets AWS deployments and recommends Sumo Logic and New Relic for observability; reports a split-site team (Waltham and Barcelona) as a working example.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:57Software Lifecycle
- 2:20The complications of continued ownership
- 5:29Sustaining Engineering as a discipline
- 6:22Let's talk staffing
- 9:20Long-term architectural changes
- 11:47A common problem: the wet basement
- 13:03Transitioning a service
- 15:23Services to transition
