awesome-talkscurated list on GitHubRecommends
Under “Software Development”
Feature Branching Considered Evil by **Thierry de Pauw** (DevTernity 2019) 49:38
0:00 / 0:00
#trunk-baseddevelopment#featurebranching#continuousintegration
🚀 Feature Branching Considered Evil (Thierry de Pauw )
DevTernity Conference
12K subscribers • 4 videos on Hallway
- Recommended by 3 people: 2 in engineering communities and 1 curated list.
- Presented by Thierry de Pauw
- An opinion. It argues one side of a question engineers disagree on.
Intermediate. Assumes working knowledge.
6.8K views6 years ago3 recommendations
Tools and practiceSystems programmingCI/CD and deploymentGit and version controlCode review and teamwork
Thierry de Pauw argues against long-lived feature branches and explains how trunk-based development improves software delivery flow and stability.
🗓️ Upcoming developer events: dev.events With DVCSs branch creation became very easy, but it comes at a certain cost. Long living branches break the flow of the software delivery process, impacting stability and throughput. The session explores why teams are using feature branches, what problems are introduced by using them and what techniques exist to avoid them altogether. It explores exactly what's evil about feature branches, which is not necessarily the problems they introduce - but rather, the real reasons why teams are using them. After the session, you'll understand a different branching strategy and how it relates to CI/CD.Why it's here
3 people recommend thisWhat people say. Recommended as a compelling argument for trunk-based development and continuous integration over feature branching.
u/Auslegungin r/ExperiencedDevs • Recommends
On “Dev workflow for medium to large teams”
I always advocate for trunk based development link to this video According to Accelerate and Google‘a research, trunk based development is a marker of a high performing team.
And when I say trunk based development I mean no branches, just main. Maybe occasionally you’ll need a branch but that’s the exception. I’m sure I’ll get a lot of “but what about…”, so I recommend the YouTube video I linked above. It addresses a lot of concerns.
u/total-antler-insurerin r/ExperiencedDevs • Recommends
On “How do you work in a trunk based development”
Really disappointed in most of the other answers that mostly say, “tbd can have short lived branches.” Technically true, not addressing OP’s question, and “short lived” needs to be defined (it should be measured in hours, not days).
But this answer is good. I’d add pair programming to the list of things to do. Pair programming often makes code review unnecessary since that already happened to a much higher degree than any 20-minute code review with a LGTM response.
Also this video is good link to this video