DevOps for developers (or maybe against them?!)
summary
Argues DevOps started as an ops-driven graft onto developers, citing The Phoenix Project and DevOps Handbook, and traces adoption through State of DevOps reports that now show 208x more deployments for elite teams. Explains tooling demands — Kubernetes Docker Terraform YAML — and why teams test in production, introducing testing in production and blast radius mitigation and feature flags. Gives concrete SRE-driven requirements (stateless services, fast start/stop, observability), a Kafka case that reduces cloud bills, and why developers must become T-shaped.
AI-written summary · about
chapters (7)
- 0:00Start
- 11:57TYPES OF WORK IN THE PHOENIX PROJECT AND DORA REPORT
- 14:20Becoming a full-stack developer
- 15:23SOFTWARE CRAFTSMAN DEFINITION OF DONE
- 18:36CODE QUALITY IS NOT ENOUGH
- 34:50DEVOPS IS A MEAN TO AN END
- 40:57Yes, DevOps is an Ops idea
related talks
41mDevOps for Java Developers (or maybe against them?!)
31mDevOps for Java Developers (Or Maybe Against Them?!)
37mDevOps for Java Developers (Or Maybe Against Them?!)
57mDevOps for developers or against them. Barukh Sadogursky. Java Fest 2020 Online
46mDevOps for Java Developers (or maybe against them?!)
16mDevOps - Philosophy vs Practice
25mDevOps for Pointy-Haired Bosses
34mDevops or: How I Learned to Stop Worrying and Love the Ops Team
