Also, when you put your name anywhere in the file, since not only the code is going to outlive you career there, I can get more detailed information from the VCS. It's like a badly drawn graffiti tag.
Some of us have done too much work in environments where VCS scares people.
Actually, when I worked with UniBASIC/Datatel, VCS was basically impossible because the architecture was so bizarre. Unless I wanted to write my own, and of course I had actual tasks I was trying to accomplish and writing a VCS was not really worth it if I couldn't get anyone else to use it.
Better to adopt the habit of copying database records (which doubled as source files) with a note of the date and my initials, since that's how it was done. Well, also I did quit.
One nice use of git in this circumstance is just turning some directory into a versioned directory. Then every time you work on it, you commit everything that's there with a comment "all the shit everyone else did since I last touched it", then you have a nice record of what you did and also big clusters documenting whatever fuckups may have occurred.
I seriously considered it. It probably would have worked, since database tables were implemented as delimited text files. [1][2]
But our vendor had their own deployment system, and there was zero chance of them sending us Git patches instead of their proprietary ones, and most of what we did was integrate patches from the vendor into our code. So really I took the only option available to me.
Also, when you put your name anywhere in the file, since not only the code is going to outlive you career there, I can get more detailed information from the VCS. It's like a badly drawn graffiti tag.