Adding Developers to the DevOps Process
summary
Company moves developers into Chef-led deployments to reduce ops burnout and speed releases. Developers learn Chef and get AWS credentials, ops adds Test Kitchen and code review, and cookbooks are refactored so manual tests drop from ~60 minutes to ~20. Adoption grows to 59 contributors over ~18 months, turning server setups from weeks to minutes. Pitfalls: steep Ruby/Chef learning curve, flaky/outdated docs, long tests and legacy anti-patterns, offshore time zones and the initial ops review bottleneck.
AI-written summary · about
chapters (24)
- 0:00Start
- 0:24ABOUT ME
- 1:58BEGINNING ARCHITECTURE
- 2:25LET'S USE CHEF!
- 3:37CURRENT ARCHITECTURE
- 4:21OPS' VIEW
- 6:03DEVELOPER'S VIEW
- 8:36COMPANY VALUES
- 9:41DECISION POINT
- 10:13ACCESS GRANTED
- 10:33CHEF DEEP DIVE
- 10:43AWS CREDENTIALS
- 12:20NOW WITH TESTING!
- 12:51GAINING STEAM
- 14:34MORE KNOWLEDGE SHARING
- 15:40DEVELOPER DOCUMENTATION
- 16:06BUMPS ALONG THE WAY
- 16:17LEARNING CHEF
- 17:35EXISTING ANTIPATTERNS
- 21:07TIMELINE
- 21:35CURRENT CHEF REPOSITORY
- 22:49WORKING TOGETHER
- 23:18WORK IN PROGRESS
- 23:44LOOKING FORWARD
related talks
27mDevOps and Baking
22mA Healthier Software Development Life Cycle with DevOps
46mDevOps for Java Developers (or maybe against them?!)
36mDevOps in Outsource… Really!
44mDevOps for developers (or maybe against them?!)
27mTaming the Kraken - How Operations enables developer productivity
25mDevOps for Pointy-Haired Bosses
25mDevOps Handbook Experiments in Accelerating Delivery