Turning DevOps Inside-Out
summary
Argues DevOps must flip to be driven by customer signals not CI scripts and shows concrete tactics: instrument with Ahoy and Blazer, mount Blazer and query Ahoy events for weekly trends, extract a controller action as a small reporting app via config.ru per-action rackup and deploy it in its own container to isolate failures (blast radius) — CPU spikes go to 100% on a monolith, containers scale in milliseconds so containers start in ≈1s vs EC2 30–60s, increasing feature velocity and targeted refactors.
AI-written summary · about
chapters (6)
- 0:00Start
- 3:52What Is Devops
- 7:07How Does all of this Impact Our Development and Operations
- 12:02Controller Actions
- 14:42Quiz Controller
- 19:39Feature Velocity
related talks
37mDevOps, 12 Factor and Platform Engineering
46mDevOps for Java Developers (or maybe against them?!)
30mA Story of DevOps Transformations
28mDevOps, 12-Factor, and Platform Engineering
58mDevOps for Frontend Engineers
56mDevOps in a containerized world
05mAdventures In Enterprise: Lessons Learned Promoting DevOps In A Legacy Organization
58mDevOps @ Scale — Greek Tragedy in Three Acts
