You don't need permission to do that
summary
Joined a managed service provider and given production SSH and sudo access, a developer cuts a 25-minute cycle by splitting 25 front-end apps out of one giant Jenkins job, writes separate repos and build plans, and automates deployments despite inheriting Chef cookbooks and shell scripts. Team adopts Kubernetes, spins namespaces in Google, port-forwards services to local machines, and repeatedly breaks then fixes pipelines — the changes land and development speed improves.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:44Could you lower your hands
- 2:08Introduction
- 4:05Why you dont need permission
- 10:19Saras background
- 11:50First emotion
- 12:30Past work
- 14:33Trust
- 17:06Humility
- 18:04Opening up the world
- 20:09Who am I
- 22:44Context matters
- 26:33Learning from operational people
- 31:16How to avoid a situation
- 34:51Limits on what a developer can do
related talks
34mFrom Dev to DevOps
58mHow I became a tester!
45mUpskilling and Retooling your team with Skill Sprints
01h 02mCracking Collaboration: Problems and Solutions for C++ Development
36mDevOps in Outsource… Really!
42mStart Small, Scale Big: Building and Scaling Platforms and SRE Culture...
34mFrom a Backend Developer to DevOps - THE FORCE AWAKENS
12mKeynote: What It's Like to Bring DevOps to a Software Factory in Central America
