Devops As Engineer Empowerment
summary
A migration to kubernetes finishes but an engineer deploys and production 500s because of a missing env var, the rollback pipeline always pulls latest, the devops lead fixes it with a laptop and pizza while the deployer gets a 403 permission error from the CLI and wonders what a kubeconfig is. The claim: DevOps often disempowers engineers. The fixes are concrete: build a safe playground environment, teach deployment mechanics, expose monitoring and rollbacks, and give scoped access so engineers can act without breaking the platform.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:35A familiar story
- 3:44Solution
- 6:13Educate Developers
- 8:30Playground
- 9:45Monitoring
- 11:00ACLs
- 13:20Reporting
related talks
52mDevops @Scale
41mDevOps for Java Developers (or maybe against them?!)
27mThe curious case of the DevOps engineer and other things ...
44mDevOps for developers (or maybe against them?!)
47mDevOps or DevX – Lessons We Learned Shifting Left the Wrong Way
45mDevOps Is Dead, Long Live Platform Engineering!
28mDevOps meets reality
28mDevOPs Lessons for Frontend Developers
