Branching Strategies Ultimately Determine Product Complexity

on YouTube ↗05m

" summary

Branching strategy determines product complexity: keeping to trunk-based development with short‑lived branches and frequent merges plus feature toggles yields far less overhead than long‑lived release branches or git flow, which multiply work‑in‑progress and force maintenance of many parallel lines of code. Complexity grows faster than linearly as branch count rises, wasted effort accumulates when changes never reach production, and frequent small merges noticeably speed delivery and reduce integration pain.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 2:08Git Flow
3. 2:23Trunk Based Development
4. 2:53Feature Toggles
5. 3:23Still Have A Problem
6. 3:53Problem 1: WIP

" related talks

• 41mA Branching Strategy For You?Simon Berner · DevDays Europe 2022
• 50mFeature Branching considered EvilThierry de Pauw · OSDC 2019
• 58mFeature Branches And Toggles In A Post-GitHub WorldSam Newman · NDC Oslo 2017
• 38mFeature Branching is EvilThierry de Pauw · TestCon Europe 2023
• 44mBranch By AbstractionPaul Hammant · Agile India 2020
• 18mTrunk Based Development and Feature TogglesLeena S N · Agile India 2020
• 39mOur journey from Gitflow to Trunk Based DevelopmentLudovic Toison · code.talks 2023
• 35mIncrease Agility and Quality Using Trunk-Based Development in Continuou...Hope Lynch, Logan Donley · cdCon 2022