Slashdot Mirror
Developer Accidentally Deletes Three-Month of Work With Visual Studio Code (bingj.com)
New submitter joshtops writes: A developer accidentally three-month of his work. In a post, he described his experience, "I had just downloaded VScode as an alternative and I was just playing with the source control option, seeing how it wanted to stage -- five thousand files -- I clicked discard... AND IT DELETED ALL MY FILES, ALL OF THEM, PERMANENTLY! How the f*uk is this s*it possible, who the hell is the d******* who made the option to permanently delete all the files on a project by accident even possible? Cannot even find them in the Recycle Bin!!!! I didn't even thought that was possible on Windows!!! F*ck this f*cking editor and f*ck whoever implemented this option. I wish you the worst.'
So the guy made a mistake using the code management software, and didn't have a backup, and it's Microsoft's fault? Is this guy on the Trump staff?
I don't respond to AC's.
Sounds like he's a diploma-mill coder who doesn't understand such things. 3 months was probably his entire career...
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
A developer accidentally three-month of his work.
I think someone accidentally a word.
And what the hell is a "three-month"? If that was ever a thing, it hasn't been for about 300 years.
systemd is Roko's Basilisk.
"I pushed that big red button and it FUCKING NUKED NORTH KOREA!
Fuck you, fuck you, fuck you, why would anybody design such a piece of crap!
Fuck you, joint chiefs of staff!
Fuck you, football carrier!
Fuck you, Microsoft, or whoever designed that ugly piece-of-shit fat green-screen laptop!
Fuck you, Dr. Strangelove! How did we ever hire such a wacko? Nice salute, though! You should
have fixed that thing a long time ago! I saw the documentary!"
(Sorry, I'd meant to post this in ALL CAPS, but Slashdot needed to protect everyone from my YELLING...)
This guy seems to have learned this lesson by displacement. "fuck you fuck you you're all morons fuck how are you so fucking stupid you deleted my files you fucking fucker morons!!!!"
Sometimes, shit is somebody else's fault; you should probably learn to deal with that, too. This is why I don't just blindly stop at a stop sign, wait 3 seconds, then pull through: the next guy might be about to plow through his red light at 90 miles an hour; maybe I should look first to ensure he isn't a moron.
This kid will probably die on a motorcycle. Don't let him get one.
Support my political activism on Patreon.
Is it ok if we call this developer a git?
He didn't know it was possible to delete stuff in Windows without going to the recycle bin.
LOL
he doesn't have any code left to store, so it's a non-issue!
What kind of a developer doesn't know that Windows programs can permanently delete its own data files?
I think we know what kind.
What kind of idiot only has one copy of 3 months of work?
No doubt.
I once worked with a guy who had the opposite problem. He did not trust the version control system, or much of anything else. He'd check the source out, copy it once onto a USB drive and a second time to his work directory. Then he'd remove the USB drive and put it in a drawer for safekeeping, then proceed to work on the code. Periodically he'd stop and copy his changed files to the USB drive. When he had completed some work, he'd copy the changed files over to the checkout location, then commit the change to the version control system.
Where it got really nightmarish is when he had multiple changes in progress at once. He'd have a checkout for each stream of work, plus a copy of each checkout on a USB drive, plus a work directory for each. He tried very hard never to do that, which meant he was always refusing to fix important bugs because he was already working on something else, even if what he was doing was less important, just because it was too hard for him to context switch due to his lame system.
If you're wondering how he kept everything straight, he didn't. He frequently forgot a file or two when copying from his work directory to the checkout, resulting in commits that didn't build because they were missing part of the change (even worse was when they *did* build). Once in a while, he copied from the wrong work directory. As far as I could tell, he never actually used the USB drives for anything at all, just copied to them and put them in a drawer.
What about merge conflicts? Heh. Merge conflicts terrified him. He was always trying to convince people not to touch any file that he was working on, and advocating for replacing the version control system with one that used a locking model, so he could lock "his" files and be sure that no one else could work on them.
I was a contractor and only worked at the place for about two months. I still felt like strangling him; I don't know how the others who had to deal with him long-term did it.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.