DevOps before there was "devops"
summary
Claim: DevOps practices predate the term and arise from pragmatic fixes. An engineer unplugs patch‑panel cables, uses a tone generator, maps 70–80 connections, and reduces a task from one to two days to a few hours while causing brief intermittent outages. Core outcomes are concrete: iterated rapidly, knocked down silos, automated repeatable steps in head, learned from failures, and used phone call coordination to confirm fixes — a small build that actually works and reveals measurable process improvements.
AI-written summary · about
related talks
06mDevOps before there was DevOps, 20yr old style
05mDevOps A Way of Being
20mWhat is DevOps?
06mDevOps Is Older Than Me
24mHow DevOps changed the way we operate software
16mDevOps - Philosophy vs Practice
19m10 years of DevOps - Where Are We Today?
30mWhat's It Like When DevOps Is Just Another Day at the Office?