Create unfair competitive advantage w/CI/CD Pipelines

on YouTube ↗11m

" summary

Claims that matter: continuous integration requires trunk‑based development with developers merge multiple times a day into a single mainline, and continuous delivery means that mainline is always releasable with automated tests as gate to prevent regressions. The talk shows how feature toggles keep trunk releasable, cites teams burning 80 hours a week before CI/CD, and promises concrete outcomes: fewer bugs, higher code quality, faster release cadence, and less emergency overtime.

AI-written summary · about

" chapters (7)

1. 0:00CI/CD pipelines intro
2. 1:45What CI/CD means
3. 3:08Continuous integration
4. 4:52Continuous delivery
5. 6:19Automation in CI/CD
6. 7:24CI/CD benefits
7. 9:33Why CI/CD game changer

" related talks

• 46mContinuous integration - that's not what they meantClare Sudbery · Agile on the Beach 2024
• 17mCI/CD - Build/Deploy AutomationRicardo Castro · Conf42 Cloud Native 2023
• 56mContinuous Integration: That’s Not What They MeantClare Sudbery · YOW! Perth 2023
• 45mContinuous Integration: That’s Not What They MeantClare Sudbery · GOTO Amsterdam 2023
• 24mWhy, What, and How of Continuous DeliveryKohsuke Kawaguchi · swampUP 2017
• 51mBetter software, faster: principles of Continuous Delivery and DevOpsBert Jan Schrijver · Devoxx Belgium 2019
• 28mMinimum Viable Continuous DeliveryBryan Finster · Global SRE Virtual Conference 2022
• 01h 01mA team's transition to Continuous DeliveryAshley Noble · NDC Sydney 2017