3 ms·

I was just told at my day job that the team will not be using VC for tracking production analytics code because "using git is over-engineering".

• Jtsummers 7y ago
  There's a set of projects in an adjacent work group that does not use version control. Instead, they create snapshots at various stages of development (before certain formal reviews). These snapshots are fine, actually they're useful, but they don't replace version control. I had a chance to explain and demo git to one of them, who'd written some 10k lines of code between snapshots, to explain how git could help him manage his work better (easier to try things and roll them back, as the primary one). This helped, he had started to use it though I don't know if it's spread yet. Fortunately there is no opposition to version control in their group, it's just momentum keeping them from changing.
  • roland35 7y ago
    This reminds me of the comic which has a machine gun salesperson trying to sell to a medieval king who says "I can't be bothered with that, I have a battle to fight!"
• mandeepj 7y ago
  > using git is over-engineering Their compass to locate "over-engineering" is a bit off track. Engineering starts after you have put your artifacts in git or any other VC :-)
• hossbeast 7y ago
  Time to start the job hunt.
  • 0x445442 7y ago
    I can't recall if it was in Prag Prog but it's one of my favorite Andy Hunt quotes... "Change your team or change your team"