10 ms·
I have to say I struggle with advanced source control management and DVCS. Every time I have been in a development team that proposes anything more complicated
by benjaminwootton 13y ago
I have to say I struggle with advanced source control management and DVCS.
Every time I have been in a development team that proposes anything more complicated than a basic branch, I start to break out in hot sweats.
I think this has come from experiences where we have had multiple live branches and then got into a mess with merging, testing, incompatibilities, not having the right thing on the right branch etc.
When it does all work, it feels more luck than judgement.
I agree with a poster above that some of the teams that I have been on seem to spend massive amounts of time moving code between branches and accounting for it. It feels like such a drag and a distraction that it's often not worth branching even for fairly substantial changes.
I think I need to slice off a few days to really deepen my understanding of GIT or similar.
- pmr_ 13y agoIn my experience the motivation to use a particular SCM scheme is tooling. That makes some of the choices non-obvious to developers that aren't familiar with the tools and their quirks. A lot of people developing those schemes forget to answer "Why do we do this?" because it is so obvious to them and you really should ask that question.