on Whether DevOps Needs a Manifesto
summary
Argues that DevOps is not a tool — the common mistake is equating it with configuration management, Docker or the cloud — and shows that those technologies can still sit inside siloed teams. Emphasizes actual practice: empathy and communication across roles matter more than infrastructure, and organizations on bare metal can be fully “DevOps.” Calls out personal burnout from isolation and points to an operational project, K2.0 (Skyline/Oculus), for anomaly detection.
AI-written summary · about
chapters (7)
- 0:00Biggest misconception about DevOps
- 0:51How Katherine got into DevOps
- 1:46DevOps Manifesto
- 2:36DevOps Culture
- 3:10Burnout
- 3:47Isolation
- 4:10Projects
related talks
05mDevOps Is Not a Department
28mDevOPs Lessons for Frontend Developers
25mDevOps: Why do we Keep Messing Up?
51mElemental devops
16mDevOps - Philosophy vs Practice
06mDevOps is not What it Seems
57mDevOps for developers or against them. Barukh Sadogursky. Java Fest 2020 Online
45mWhat is DevOps and why should you care?
