Transitioning Ops to the Cloud, adding Dev skills to the mix
summary
Argues that Ops people move toward Dev work by adopting developer practices but should focus on processes first, not tools; demonstrates using Azure Resource Manager with Bicep (and mentions Terraform) to keep infrastructure declarative, stores templates in a centralized repo and drives deployments from source control, and shows daily scrums unblock work quickly; recommends start with templates (declarative over imperative) so automation supports business processes, not replaces them, and reports that this approach reduces version chaos and speeds feedback loops.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:39From operations to DevOps engineer
- 6:48Process improvement first
- 11:30Agile and scrum dynamics
- 14:25Daily scrum tool
- 14:47Infrastructure as code
- 19:01IaC templates start
- 22:26Q&A
- 23:07DevOps to development
- 25:20Hiring Ops vs Dev
- 25:44Internal dev platforms
- 26:06Cross-functional challenges
related talks
39mPutting the Ops in DevOps
53mDevOps and Agility with Visual Studio, Azure and Scrum
45mPlatform Engineering vs DevOps
44mDevOps for developers (or maybe against them?!)
25mDeveloper Experience is central to DevOps success
45mFrom Pets to Cattle: Learning to let go and automate
06mIgnite: Moving from regular sysadmin to DevOps
45mFrom The Iron Age To The Cloud Age