Compliance & Regulatory Standards Are NOT Incompatible with Modern Development..
summary
Argues that no law forbids practices like continuous deployment, observability-driven development, feature flags or testing in production and shows real-world fixes: Etsy, Honeycomb, Branch and others run CD and SLOs; Honeycomb replaces manual Terraform AWS access with a SAML-based Google onboarding flow (auditors accept a scripted access export). Recommends baking security into architecture, using compensating controls and measures cycle time impact—15-minute deploy vs week doubles headcount—to prove fast feedback wins while staying compliant.
AI-written summary · about
chapters (9)
- 0:00Modern software challenges
- 1:34Core devops principles
- 5:58Deployment and release
- 6:57Navigating security & compliance
- 16:48Interpreting standards
- 18:25Driving organizational change
- 26:57The role of the engineer
- 27:31Engineering effectiveness
- 36:35Conclusion
related talks
22mBridging Compliance and Innovation: A Guide for DevOps Leaders
33mCompliance as Code - Lessons Learned From Regulated Organizations
32mContinuous Delivery Sounds Great But It Won’t Work Here
48mWhen DevOps Meets Regulation: Integrating 'Continuous' with 'Government'
43mRegulatory Compliance as a DevOps Enabler
21mSecure and Fast into Production — Modern Software Development in Regulated Environments
31mWrangling Compliance in the Wild West of Software Delivery
29mAutomating Continuous Compliance for Scalable SaaS Delivery