I never trust anything but the commandline when it comes to git. Then I know full and well what I'm doing regardless of the editor. When there are too many icons and buttons to click I don't like to have to remember what they all mean, or how well they map to the underlying core git concepts.
Developer accidentally deletes 3 months of work with Visual Studio Code
31–40 of 75 posts
Re: Developer accidentally deletes 3 months of work with Visual Studio Code
#32I predict one day we will look back and be horrified that there was ever a time where you can't just roll back an entire system to an arbitrary timestamp to undo accidental changes. In some sense this is already achievable if you just always work inside a Dropbox folder (which keeps a 30 day history of any synced changes). But resources aren't yet cheap enough for all changes to be immutable.
Re: Developer accidentally deletes 3 months of work with Visual Studio Code
#33Re: Developer accidentally deletes 3 months of work with Visual Studio Code
#34He says that it wasn't in a repo, so it's a bit weird that it would delete all his files, it looks more like he had an initialised repo and hadn't committed the files yet. I don't even know how you could work 3 months without committing, even working on a throwaway thing for more than a few hours I make a new local repo, it doesn't cost much. Also the files are not gone, they are still on the hard-drive/SSD it's not…
Re: Developer accidentally deletes 3 months of work with Visual Studio Code
#35Earlier quoted context omitted.
You're blaming the victim. Yes, it's better to know git than not knowing it, but the developer was merely tossing around with the various options of the IDE. It shouldn't be that easy to make an operation with such disastrous results. It is the responsibility of the product designers to prevent this.
Certainly there might be room for improvement. But the warning was pretty clear I feel. At some point you have to take responsibility for knowing your tools. This is a professional.
He might know how to write code, but obliviousness towards source control (and backups, for that matter) is a HUGE indicator of him not being a professional.
Re: Developer accidentally deletes 3 months of work with Visual Studio Code
#36The sad part is that he didn't learn his lesson. The problem obviously isn't with Visual Studio Code, but with Git (or whatever version control software he tried out). It seems that he didn't know anything about using git and accidentally checked out a bare repo instead of adding his files to stage. From his post, he says he's using windows and he's used to things going into the recycle bin, something a Linux tool li…
You're blaming the victim. Yes, it's better to know git than not knowing it, but the developer was merely tossing around with the various options of the IDE. It shouldn't be that easy to make an operation with such disastrous results. It is the responsibility of the product designers to prevent this.
Re: Developer accidentally deletes 3 months of work with Visual Studio Code
#37Earlier quoted context omitted.
Certainly there might be room for improvement. But the warning was pretty clear I feel. At some point you have to take responsibility for knowing your tools. This is a professional.
> This is a professional. He might know how to write code, but obliviousness towards source control (and backups, for that matter) is a HUGE indicator of him not being a professional.
Re: Developer accidentally deletes 3 months of work with Visual Studio Code
#38The sad part is that he didn't learn his lesson. The problem obviously isn't with Visual Studio Code, but with Git (or whatever version control software he tried out). It seems that he didn't know anything about using git and accidentally checked out a bare repo instead of adding his files to stage. From his post, he says he's using windows and he's used to things going into the recycle bin, something a Linux tool li…
I think that the first lesson that he should learn is the need for regular backups. In fact, I am not even sure he meant to use git ("I hadn't commited any of them to any repository"). If it that's the case, I would understand why he did such a mistake: * Open the folder in VS Code * Explore around, discover the Git tab on the left, "This workspace isn't yet under git source control", press the button * "Whops, I did…
Re: Developer accidentally deletes 3 months of work with Visual Studio Code
#39The original Github issue seems to have been deleted, but here's a fresher cache that includes a response from a VS Code Microsoft employee, including a pic of what the warning dialog looks like: http://archive.is/EZX1O