Upskilling and Retooling your team with Skill Sprints
summary
Claims rapid capability building: one-week Skill Sprints embed two–three engineers and deliver real infrastructure the employees must own, turning a stalled Kubernetes adoption into an operational platform in five days and converting a PHP team to Go microservices in a week. Tool choices favor kubectl + envsubst templating and Google Cloud, explicitly avoid Terraform and Helm. Outcomes include slashed staging bills (example $2,500 → <$200) and teams that go independent and continue to evolve the pattern.
AI-written summary · about
chapters (12)
- 0:00Skill Sprints introduction
- 3:09Darwinist’s mission focus
- 10:55Why traditional training fails
- 13:42DMSI Kubernetes case study
- 19:39Imperative vs declarative explained
- 22:50Kubernetes simplifies complexity
- 26:42Hidden DevOps costs
- 30:33Google Cloud vs AWS
- 35:11Darwinist’s stack
- 38:01Q&A: Firefighting scenarios
- 41:12Q&A: Upskilling investment
- 45:02Closing remarks
related talks
39m8 Things to Consider When Skilling Up Your Dev Team
37mHow to Create Kubernetes Experts
27mDeveloping Devopsers
26mSkilling Up: How to Effectively Grow a Cloud Foundry Organization - Steve Greenberg, Resilient Scale
29mZero to SRE
12mKeynote: What It's Like to Bring DevOps to a Software Factory in Central America
24mBuilding a Cloud Native Curriculum for Real-World Readiness
45mGrowing into new roles beyond the cloud