4 ms·
...I honestly kind of agree with your department regarding points 1 and 2. If programmers never collaborate, and they have a backup system in place, then you do
by Wowfunhappy 7y ago
...I honestly kind of agree with your department regarding points 1 and 2. If programmers never collaborate, and they have a backup system in place, then you don't need git for those things.
But point 3 is a super big one, so I'd focus on that. Is there really know time when your company took something out that they realized they wanted later? There's never been a regression they had to roll back? Really?
If not, you might tell them that it's helpful to you as a programmer to be able to refer to how something was done previously.
- austincheney 7y agoI disagree in that it sounds like the OP's organization is staffing to the limitations of their technology. It reminds me of working in subversion where people would never collaborate for fear of commit collisions. This super bad from a knowledge perspective in that people don't cross train and instead become reclusive experts that they use to justify their existence and continued value. For me, personally, the biggest win of git is ease of branching allowing for rapid and easily disposable experimentation in the source code.