Excellent advice, you don’t need anything complex, just install git and you’re good to go.
Think of a commit as a save point before the boss fight. One rule is enough to start: commit every time something works, and always before trying something risky. Write the message as if for yourself in six months.
The server can wait until you have something worth losing. Just remember git on one disk isn’t a backup: copy the folder somewhere else now and then.



Loved the replies. Once it’s over (that’s the hard part), everyone has a funny story to tell!
Mine was a race condition in an outsourced core system that showed up about six months after release, only when enough transactions hit at the same moment. The contact centre was on fire, with people calling non-stop.
Same lesson as yours: when something fails only sometimes, stop staring at the code and look at what else is running at that moment.