Trusting Mission Critical Infrastructure: Building Reliable CD P...
summary
Argues that trust rests on competency empathy reliability and that platforms win by proving specific behaviors not features: adopt proven engines like Spinnaker Jenkins Argo instead of rewriting, publish a contributing.md and accept pull requests, run small pilot FaaS experiments to limit impact, separate compliance controls from best-practice defaults, and use structured feedback loops plus a clear roadmap. Claims unreliable deploys (e.g., 5/10) drive shadow tooling and overhead; these measures increase adoption and reduce forking.
AI-written summary · about
chapters (18)
- 0:00Introduction to trust
- 1:23Defining trust
- 3:06Competency in platforms
- 3:27Empathy in engineering
- 5:13Reliability over time
- 5:57Systems of enforcement
- 7:00Incentivizing wrong behavior
- 8:44Trust gap and low engagement
- 10:30Shadow systems and overhead
- 11:33Enabling trust environments
- 12:57Establishing clear values
- 14:41Leveraging trustworthy sources
- 15:43Paths to competence
- 17:49Minimizing failure impact
- 19:12Contributing.md for collaboration
- 20:14Controls vs best practices
- 22:00Summary and strategies
- 22:45Q&A on inner source
related talks
01h 04mTrust and Confidence through Chaos
41mLessons from Mission-Critical Systems in Fast-Moving Industries
26mHuman Trust in Continuos Deployment
05mBuilding resilience in our organizations...
39mPlatform Engineering as a (Community) Service
48mStrong Foundations: Insightful learning vs trial-and-error in CI/CD
59mBy Tomasz Manugiewicz
37mUntrusted Execution: Attacking the Cloud Native Supply Chain