2 ms·
At work we're just switching from a centralised VCS (not Subversion, but of similar capabilities) to Git, using Github as a central repo. We do in fact need th
by davidgerard 13y ago
At work we're just switching from a centralised VCS (not Subversion, but of similar capabilities) to Git, using Github as a central repo.
We do in fact need the superiority in branching/merging that you have with git - not having it has been a PITA several times recently. We'd really outgrown CVCS and needed what DVCS had to offer.
That said, we've been having a fun time getting used to git's little ways. Everyone's shot themselves in the foot at least once, me included. If you move from centralised to distributed VCS, you will shoot yourself in the foot unless you have an accurate mental model of what's happening.
A few developers have complained it's all too hard and complicated and they have to use the command line now (they don't) and why can't we go back to the old way. I've been reminding them programmers are supposed to be smart and able to learn things ...
The change is totally worth it, though. The pace of development has accelerated.
- nnethercote 13y agoI wonder how many of the foot-shootings are due to not being familiar with DVCS, and how many are due to git's awful UI. While DVCS is more complex than centralised VCS, git's presentation of the concepts isn't exactly clean.
- davidgerard 13y agoThe awful, awful command-line interface doesn't help. But quite a few were with the vast and excellent selection of clicky picture tools, so I mostly attribute it to attempting to get by with clicky things without understanding what's going on. Once you do, it's brilliant. tl;dr you do in fact need a basic understanding of the chain of versions and how branching actually works and stuff.