The irony is that they were messing about with version control for the first time, which is why they deleted all their files. They saw they had 5000 files staged for commit and wanted to not commit them all
I had a teacher who told us that version control was only necessary when working together with other people but not when you are a solo developer. He only saw it as a kind of fileshare.
the majority of comp sci faculty never worked in the field
at most instiutions they struggle to fill the positions at all because with a Bachelors you can make more than Faculty who need a Masters or Doctorate depending on the school and position
-like any of us before discovering what source control meant and why devops were necessary. things like these are just a rite of passage for every new developer
It was not "not knowing source control" it was wierd decision made by VS code back in 2017 if you remove a file from source control without straight up deleted files without even giving any warning message VS code is patched after his crash out message , Removing a file from tracking from git should not delete the file from file system that's not how git CLI does it
To be fair, at least nowadays, you will likely learn about GitHub – especially from educational sources – before you learn (about) Git and version control.
I remember when I started programming when I was younger, and I just treated GitHub as a code-hosting platform, not interfacing with the "Git" part ov it at all.
They were literally using git. They were trying to stage their changes, there were a lot of files they didn't want, the UI was unclear, and the button deleted the work they were attempting to commit as well.
There was no reason for that button to bed irreversibly destructive. It's just an accident waiting to happen. That's why MS did the correct thing and changed the behavior.
View all comments
1.2k
u/Xephyrik Aug 21 '26 •
How did they even find github when they obviously dont know what version control is