Back in 2016 (wow, almost a decade now…) I got a job with a group who used Word docs to email instructions on how to update your code with their changes. For example, “In file xyz.php, go to line 123 and replace <code> with <code>.”
One of my first tasks was getting that group set up with git. But I will never forget that was their best way to version control code… in 2016.
My first like real programming job, in 2019, version control was “download the project from the share drive, update the code, then add your new code back to the share with todays date in the folder name”.
Everyone, except 1 dude liked SVN or mercurial, wanted the boss to just get us on git. It became the general standard for a reason. None of us liked the version control system we had, but HDD space was cheap so the boss wasn’t that concerned.
Back in 2016 (wow, almost a decade now…) I got a job with a group who used Word docs to email instructions on how to update your code with their changes. For example, “In file xyz.php, go to line 123 and replace <code> with <code>.”
One of my first tasks was getting that group set up with git. But I will never forget that was their best way to version control code… in 2016.
I requested a code snippet and instructions for work, I got an email, with a word document attached.
In the word document there was a screenshot of the code I needed.
My first like real programming job, in 2019, version control was “download the project from the share drive, update the code, then add your new code back to the share with todays date in the folder name”.
Everyone, except 1 dude liked SVN or mercurial, wanted the boss to just get us on git. It became the general standard for a reason. None of us liked the version control system we had, but HDD space was cheap so the boss wasn’t that concerned.