Programming to the extreme
summary
A consultancy team (ThoughtWorks) describes a working day where developers sit together, pair eight hours a day pairing and follow tests first (TDD), trunk-based commits and an automated CI/CD pipeline that pushes green builds from stage to production. The process targets ten-minute CI runs, uses a single shared branch, and supports a nine-person team with one remote node on a continuous video link. Claim: shipping every commit to production is routine and dramatically improves feedback and quality.
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker intro
- 0:20What is extreme programming
- 1:53Values behind extreme programming
- 3:16Core values explained
- 5:04Principles as a bridge
- 7:01Practices in extreme programming
- 9:10Pair programming explained
- 10:14Test-driven development
- 10:56Daily deployment and delivery
- 11:58Real-world scenario walkthrough
- 16:54Key takeaways and benefits
- 17:59Change starts with awareness
- 18:40Success needs technique and relationships
- 19:50Q&A on team collaboration
related talks
45mContinuous Integration: That’s Not What They Meant
47mContinuous Delivery Warstories
56mContinuous Integration: That’s Not What They Meant
01h 01mA team's transition to Continuous Delivery
41mShift Left, Shift Right and Improve the Centre
36mHow programmers & testers can be productive
38mBuilding a high quality product
46mContinuous integration - that's not what they meant