2 ms·
Their last rebuttal is the problem. You could easily counter the others. First rebuttal: > We store code on a network share, which is backed up automatically
by Jtsummers 7y ago
Their last rebuttal is the problem. You could easily counter the others.
First rebuttal:
> We store code on a network share, which is backed up automatically every night.
Git (and other version control systems) permit more frequent backups independent of policies established by the sysadmins.
Second rebuttal:
> We rarely have multiple people working on the same system at the same time - the benefits will be negligible, and only add complexity to our daily work (this is true, work here is very silo'd).
If most things are only touched by one person, then git (and most other version control systems) add negligible complexity. While not advisable, you could even have them work off of master (as they do now anyways). [This lets git be a gateway to process improvement. Once they see the fine-grained snapshots and realize they could have people work on the same code at the same time, they may start using branches and other capabilities.]
That last one, though, indicates they don't actually care about anything. The past is not gone. Having these snapshots lets you do a lot of useful things like git bisect. Or the ability to easily rollback to a known good state. If they really don't care about that, I'd run, not walk, to the nearest exit.