The continuous culture

on YouTube ↗59m

" summary

Argument for moving beyond continuous delivery to a culture that makes rapid, safe experiments: claim that high performers run 2555x faster (Puppet Labs) and examples like Amazon deploying every 11.2 seconds motivate daily or more frequent releases; practical tools and failures include ELK stack monitoring, UpSource code reviews, JIRA-driven release notes, and a botched six‑month period of “green” tests pointing at an empty dataset. Concrete outcomes: break a 60,000‑line COBOL mess into 15,000 lines, adopt microservices, and prefer incremental delivery over risky branching.

AI-written summary · about

" chapters (49)

1. 0:00Intro
2. 0:25About Kim
3. 1:37The continuous culture
4. 1:56About Alpha
5. 3:20Going faster
6. 4:21The Dutch landscape
7. 5:22Kinetic framework
8. 8:10Experiments
9. 9:11The Standish Manifesto
10. 9:37Feedback value
11. 10:37Feature usage
12. 11:41Innovation
13. 12:14Flow value
14. 14:07How to deliver incremental change
15. 14:33What is continuous delivery
16. 15:25What is continuous
17. 18:27Incomplete tests
18. 20:03Continuous delivery
19. 20:38Maturity model
20. 21:32Level 1 Continuous Integration
21. 22:51Level 1 Practical
22. 29:59Agile Product Management
23. 31:36Lean Product Vision
24. 33:22Audit Compliance
25. 35:56Compliance Requirements
26. 37:28JIRA Integration
27. 38:20Agile HR Manifesto
28. 39:24Managers believe that matters
29. 39:53Change the way we do performance reviews
30. 42:11How many times are you breaking things
31. 42:34Feedback is fun
32. 43:05Giving space
33. 43:50Team autonomy
34. 45:47Continuous learning
35. 46:45Knowledge events
36. 47:08Hackathon
37. 47:46Architecture
38. 48:32Microservices
39. 49:09Test pyramid
40. 51:07Cucumber vs imperative
41. 52:06Branching
42. 52:29Shipping choice
43. 52:42Integration tests
44. 53:45Shipping delay pyramid
45. 55:21Customers dont want continues delivery
46. 55:44Legacy code and broken trust
47. 56:43Improve and accelerate
48. 58:04Autonomous teams
49. 58:19Evolutionary architecture

" related talks

• 31mThe Continuous CultureKim van Wilgen · The Lead Developer New York 2018
• 40mSustainable Continuous Delivery: Patterns for rapid and reliable ReleasesManuel Pais · DevOpsCon Spring 2019
• 55mThe Rationale for Continuous DeliveryDave Farley · GOTO London 2015
• 33mCulture of Continue DeliveryLeena S N, Vaidy Bala · RailsConf 2014
• 36mWhat do we know about continuous delivery – and what would we like to knowLars Bendix · Incontro DevOps 2017
• 51mBetter software, faster: principles of Continuous Delivery and DevOpsBert Jan Schrijver · Devoxx Belgium 2019
• 33mContinuous Delivery - What does good really look like?Dave Farley · CI/CD Express Conference 2023
• 32mContinuous Delivery Sounds Great But It Won’t Work HereJez Humble · DevOpsDays Seattle 2017