From Deming to DevOps
summary
Deming’s System of Profound Knowledge maps to today’s DevOps and AI risk landscape: teams reuse Kafka, Redis, Kubernetes and vector databases to move notebooks into production, creating a vector DB sprawl and a predictably huge technical-debt wave. An experiment shows a poisoned inference on Hugging Face that escapes a container to a shared host, proving infrastructure risk is real. Corporate surveys find 78% BYOA (bring‑your‑own‑AI). Operational definitions, PDSA cycles and control‑chart thinking are the countermeasures proposed.
AI-written summary · about
chapters (14)
- 0:00Introduction and name origin
- 2:15Speaker’s background and career
- 6:47Technical debt and system thinking
- 9:17Abraham Wald’s bullet hole story
- 10:21Deming’s operational definitions
- 13:08Shadow AI and governance concerns
- 15:16Why Deming matters today
- 18:28Deming’s system of profound knowledge
- 21:15Dear CIO: Technical debt tsunami
- 24:49AI infrastructure and threats
- 27:14Prompt injection and security risks
- 28:39Abductive reasoning and AI
- 30:24Operational definitions and guardrails
- 32:54Summary and call to action
related talks
25mDeming to DevOps (Revisited)
29mBringing Decades of DevOps Experience To Deep Learning
31mRethinking DevOps and DevSecOps with Generative AI: Insights
29mThe Future of DevOps: AI, Security, and Next-Gen Collaboration
30mDevOps For Data Teams
40mDistilled Abnormal DevOps Iterations
29mHow to use AI to fight your DevOps transformation!
59mDevOps for Data Science