Keynote - The gordian knot
summary
Survey data shows high performers deploy up to 46x more frequently and achieve 400x faster lead time than low performers, with lower mean time to recover and fewer change failures. Architecture and culture mutually shape outcomes: hiring “DevOps” or ripping out a monolith alone fails; microservices without bounded contexts often keep old coupling. Practical levers are tight feedback loops, shorter delays, and loose coupling so small teams own small slices and get rapid, visible feedback that drives learning and purpose.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 1:14The impact of DevOps
- 3:32Microservices challenges
- 6:31Culture and architecture
- 9:33Defining culture through design
- 15:26The Pink and feedback checks
- 22:31Importance of feedback cycles
- 29:44Engineering sadness scenarios
- 36:21Final summary and conclusion
related talks
53mHatching software development ecosystems (the gordian knot)
53mKeynote - Software Architecture, Team Topologies and Complexity Science
01h 00mKeynote: What really matters
49mKeynote
52mKeynote: The Psychology of Code
58mKeynote: Seven Habits of a (Mostly) Successful Team
37mKeynote - You are Load Bearing
53mKeynote: Value Driven Development - Maximum Impact, Maximum Speed