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.'

765 comments

  1. Version Control = Good by brian.stinar · · Score: 5, Insightful

    This is why offsite backups, and revision control, is a good idea...

    1. Re: Version Control = Good by Anonymous Coward · · Score: 0

      I've seen it delete the .git dir before so unless you also push it to a remote, that won't necessarily help.

    2. Re:Version Control = Good by Anonymous Coward · · Score: 5, Insightful

      What kind of idiot only has one copy of 3 months of work?

    3. Re:Version Control = Good by Shatrat · · Score: 4, Funny

      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
    4. Re:Version Control = Good by Aighearach · · Score: 5, Informative

      This isn't about backups, it is about not having a central repository. It isn't enough to have revision control, you have to actually be checking it in to a repository and sharing code. Even if you're only sharing with yourself, you still want your revision control to work well. And if you're not synchronizing anything, then you're not even getting feedback about if the system is working.

      It isn't enough to commit the code, you also have to push it somewhere. Even if that is just a repo on the same box.

      You don't want to restore this situation from backups, you want the restore to be from the repo. Much simpler and more to the point. And the backup would be of the repo, not the working directory!

    5. Re:Version Control = Good by djinn6 · · Score: 3, Informative

      You don't even need a central repo. For small projects I just zip the .git directory and upload it to Dropbox or Google drive once or twice a week.

    6. Re:Version Control = Good by ShanghaiBill · · Score: 1

      This isn't about backups, it is about not having a central repository.

      Actually, it is about having neither.

      Also, it is about failing to understand how filesystems work, and how to use Google. It is possible he could have "undeleted" these files with a bit of work. It sounds like all he did was look in the Recycle Bin.

    7. Re:Version Control = Good by Z00L00K · · Score: 4, Interesting

      He was from I understand trying out a revision control system that was pretty buggy.

      In general I have found out that source control systems related to the Microsoft environment are tricky. They used to have something called Source Safe, it was fine until the repository disk was full, then you lost everything.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    8. Re:Version Control = Good by l0n3s0m3phr34k · · Score: 1

      It's not like there aren't even any free apps he could try...it took me longer to make the post than to find all of these.

    9. Re:Version Control = Good by rholtzjr · · Score: 2

      Yes, that happened at a company I was at as well. The Windows dev team was frantically asking "what date was the last back up done" to the infrastructure team. We over on the Unix side of the house breathed a sigh of relief as they were asking all of us to consolidate our repositories into SourceSafe but we voted it down just 2 weeks prior.

    10. Re:Version Control = Good by Austerity+Empowers · · Score: 2

      The workflow that I'd advocate is to make a bare repo on some other machine that is backed up, clone that repo and keep your code on your dev machine. Edit/commit/push back there. This gives you all the advantages of git, particularly if you ever need to use another machine for dev without exposing your entire codebase to HD wipes, or ... microsoft's evil software quirks.

      Zipfiles and tarballs automatically snapped periodically are good as backup, but are kind of annoying to work with, particularly if his tool does something more subtle and he wants to go back in time to just before it happened. There was an editor I used to use that had a habit of corrupting it's own project files in subtle ways, and what i ended up having to do was get an old copy of that file, and hand tweak it in to the present format of that file so the editor would stop being stupid. git really helps here.

    11. Re:Version Control = Good by Anonymous Coward · · Score: 0

      Title should be "Novice Developer-in-Training Learns Valuable Lesson"

      Always make backups. Especially if you are playing with new software. Copy your shit before you let the new software touch your stuff. So he's 3 months into being a 'developer' and learned this. Not too bad, he could be further into his career. So this looks like a cheap mistake to learn from for him.

      I bet he makes a copy of his files next time.

    12. Re:Version Control = Good by hey! · · Score: 2

      And now he will never use source control again....

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    13. Re:Version Control = Good by F.Ultra · · Score: 5, Interesting

      I don't think that Source Safe ever works fine for any definition of the word. Back some 12-15 years when I was working at a "Omg we can only use Microsofts products" place it was common to see our dev chief roll back the entire Source Safe repository from backups. Some times I saw him do this on a daily basis. Another fine touch where when some dev checked out some files and went on a 5 week vacation leaving the file locked in Source Safe, not the good old days :)

    14. Re: Version Control = Good by bobbied · · Score: 4, Insightful

      I've seen it delete the .git dir before so unless you also push it to a remote, that won't necessarily help.

      Offsite backups, file system backups, wayback machine? Any of these works with Git... Of course, why use Git if you only keep one repo laying around...

      BACKUP your important stuff or stupid mistakes will cost you..

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    15. Re: Version Control = Good by tk77 · · Score: 5, Insightful

      What? Why not? Git is perfectly fine for a single developer. I use it all the time on personal projects. You can even create multiple local repositories so if you screw up your primary tree you can easily recover it.

    16. Re:Version Control = Good by Lord+Kano · · Score: 3, Informative

      You're probably right.

      Judging by the name, it would appear that this guy only graduated high school 2 years ago and recently graduated a free coding camp.

      LK

      --
      "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
    17. Re:Version Control = Good by Nemyst · · Score: 1

      It's literally a GUI wrapper over Git. It's as stable or buggy as Git is. There was no bug at play here, merely an incorrect understanding of Git/VSCode terminology, a failure to use a test environment for testing (testing directly on your main project is not smart) and especially a failure to have any sort of backup or SCM.

    18. Re: Version Control = Good by Anonymous Coward · · Score: 2, Funny

      He didn't know it was possible to delete stuff in Windows without going to the recycle bin.
      LOL

    19. Re:Version Control = Good by rogoshen1 · · Score: 5, Funny

      he doesn't have any code left to store, so it's a non-issue!

    20. Re:Version Control = Good by JohnFen · · Score: 1

      This, precisely. There's nothing wrong with git, but nobody should be keeping the repository on the same machine they're developing on.

      At a bare minimum, if you keep it elsewhere (even on a small machine in the corner of the same room), then you always have two copies of your work.

    21. Re: Version Control = Good by bobmajdakjr · · Score: 1

      been on vs code insiders since day one. never once. guess not being bad helps lol.

    22. Re:Version Control = Good by Anonymous Coward · · Score: 0

      He deleted his github after this story went out, so doesn't have version control anymore...

    23. Re: Version Control = Good by Anonymous Coward · · Score: 0

      Me too, for the same reason. And you back both up using rsync, regularly.

    24. Re:Version Control = Good by Anonymous Coward · · Score: 0

      Or you could just run the version control repo locally, and back the repo up to a USB stick,
      or anywhere else (like Dropbox or Google drive) for that matter.

      That way you still have the benefit of version control.

      Amazing in this day and age how the coding schools don't teach something so simple.

    25. Re: Version Control = Good by tk77 · · Score: 1

      I use a remote bitbucket on a personal vm, but same deal. Can even just set up a remote repo over ssh.

    26. Re:Version Control = Good by JaredOfEuropa · · Score: 1

      If I do anything with a new source control system (or anything else that messes with my files, like encryption or backup software) that I am "trying out", i.e. do not yet fully understand, I back up whatevery I am checking in or adding to the repository. Not offsite,nothing elaborate, CTRL-C, CTRL-V to a different disk, done. Once I am fully comfortable with the software I might get rid of the copy.

      --
      If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
    27. Re: Version Control = Good by Anonymous Coward · · Score: 0

      Why use git? How about branching, simple backups using remotes to name just a couple.

    28. Re:Version Control = Good by taustin · · Score: 5, Funny

      What kind of a developer doesn't know that Windows programs can permanently delete its own data files?

      I think we know what kind.

    29. Re:Version Control = Good by nine-times · · Score: 2

      Yeah, I'm not trying to defend VS Code. I use it and find it useful (writing Powershell scripts on a Mac), but for the sake of argument I'll concede that it's a terrible tool and that Microsoft is the devil himself. Still, that doesn't explain how a developer lost 3 months of work.

      Because if you're playing with a new tool that includes file editing and file management, it's not a good idea to experiment and test it out in a production environment with files that you rely on. Even if he hadn't accidentally deleted his files, it wouldn't be unheard of for a text file editor to alter the files in some way. Even if it just changes the encoding, that could break things and cause problems.

      But regardless of all of that, where are the backups? Who, in this day and age, doesn't know that you should back up your important files? If you're any kind of computer professional, not having backups is kind of inexcusable.

    30. Re:Version Control = Good by Anonymous Coward · · Score: 0

      I was surprised the rant in TFS didn't include a 50 DKP MINUS! F*uk!!!!!!

    31. Re:Version Control = Good by Anonymous Coward · · Score: 0

      Source safe was a piece of shit, but as long as you knew its limitations and bugs, it was kind of usable. At the time, version control systems with similar price tag (SS was part of MSDN subscription which all Windows developers had anyway) were such gems as CVS and RCS. If your admin did not even know how to use the SS admin tool to unlock a file, no wonder you were in daily trouble.

    32. Re:Version Control = Good by Anonymous Coward · · Score: 0

      As far as I'm concerned most Microsoft tools are complete shit. Everywhere I've worked that has been a Microsoft shop has been a complete disaster with tons of finger pointing everywhere and always massively stressed out.

      Captcha: usable

      That sums up Microsoft quality rather well.

    33. Re:Version Control = Good by chipschap · · Score: 2

      If this guy was so clueless/inexperienced to not have a separate backup (off-site, in the cloud, wherever) then he has learned a difficult lesson. He can blame the tools all he wishes, but the fault lies squarely with him.

      I'm obsessive about backups. There's a reason for that. Things go wrong all the time.

      Full disclosure: I once lost almost 10,000 words of a novel I was writing due to my own cluelessness about certain backup systems. It was a hard lesson.

    34. Re:Version Control = Good by Anonymous Coward · · Score: 0

      Either Lazy or Clueless. Either way negligent.

    35. Re:Version Control = Good by 93+Escort+Wagon · · Score: 1

      Back some 12-15 years ... it was common to see our dev chief roll back the entire Source Safe repository from backups. Some times I saw him do this on a daily basis. Another fine touch where when some dev checked out some files and went on a 5 week vacation leaving the file locked in Source Safe, not the good old days :)

      Except for the "Microsoft" part, this sounds a whole heck of a lot like the modus operandi of a boss and one particular co-worker I had at roughly the same time as you!

      Thank God neither one of them is around here anymore... so much of my time, back then, was spent cleaning up after their messes.

      --
      #DeleteChrome
    36. Re:Version Control = Good by 93+Escort+Wagon · · Score: 1

      It's a win-win!

      --
      #DeleteChrome
    37. Re:Version Control = Good by F.Ultra · · Score: 1

      Of course you could use the SS admin tool to unlock a file, but that required admin rights which you would never get as a plain dev there. So you had to file a unlock request and hope that it would be solved some day in the future. For all the warts with CVS it is nowhere as much trouble as SS. I think that one of the main problems with SS is that it used the windows file share as it's transport protocol so if it was kind of usable for you then perhaps you didn't have to use it over a shared network with other devs?

    38. Re: Version Control = Good by Anonymous Coward · · Score: 0

      So what should he be using?
      subversion?
      cvs?
      zip files scattered all over the place?

    39. Re:Version Control = Good by swillden · · Score: 5, Funny

      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.
    40. Re:Version Control = Good by Threni · · Score: 1

      Get a raspberry pi and a 16gig sd card. Create git repositories for all your local repositories. Every once in a while push your data there.

      If you lose 3 months work because you didn't know what you're doing, tried something, didn't read a message, and didn't have backups you're not a developer - you're just a fucking idiot.

    41. Re:Version Control = Good by PmanAce · · Score: 1

      TFS is rock solid, he was using Git.

      --
      Tired of my customary (Score:1)
    42. Re:Version Control = Good by skids · · Score: 1

      Think of it as the snake eating it's own tail.

    43. Re:Version Control = Good by Anonymous Coward · · Score: 0

      Well, he'll just never get employed in this industry then I guess (not that I'm seeing this as a loss, based on what I'm reading)

    44. Re:Version Control = Good by Anonymous Coward · · Score: 0

      ... most of us.

    45. Re:Version Control = Good by Darinbob · · Score: 1

      And never treat revision control as backup. Yet so many people do this. Ie Friday night they check their code in whether it works or not, and to the mainline branch. Had one coworker who checked in changes every few minutes, no matter the state of the code (I suspect he set up his editor to automatically commit after every save). I've had coworkers vigorously defend this practice essentially saying that they need to backup the files and arguing against having continuous builds because they were always the ones to be blamed when the build broke every few hours.

      So, use revision control, and get a backup system that works and is convenient. Time Machine for OSX is awesome, just ask the boss to reimburse for the cost of an external hard drive (and encrypt it). Too bad there's nothing so painfree as that on Windows. If you can't do that, then at least get a script to copy your code to a server at the end of the day.

    46. Re:Version Control = Good by Darinbob · · Score: 1

      You want both. Don't check into the repo until the code is ready to be checked in, and code that is checked in should build cleanly and run without crashing. Use the backup for in-progress files not yet suitable for committing. If you want personal revision history prior to checking into an official repository then get a secondary tool for that. Ie, I know people who use git or mercurial for their own use so that they can commit often and then later commit the code to the company's repository, which reduces that amount of noise when reviewing revision history on a file.

    47. Re: Version Control = Good by Anonymous Coward · · Score: 0

      So was this dumbfuck fired or what?

      "I hit delete and everything got deleted! Not my fault!"

    48. Re:Version Control = Good by Anonymous Coward · · Score: 0

      I just upload mine to The Pirate Bay and name it something involving the word "insurance." The internet does the rest.

    49. Re:Version Control = Good by ponfgong-e · · Score: 1

      For Real. LOL. No backup and then you throw a tantrum when you lose files. Bugs happen, if it wasn't vs code could have been a lightening strike, live and learn.

    50. Re:Version Control = Good by Anonymous Coward · · Score: 0

      What kind of idiot only has one copy of 3 months of work?

      A developer. You never ever ever let developers administrate machines. The whole of DevOps is only possible because you can now lie to developers and tell them that a program running on your server is a "virtual machine" and then secretly back it up from underneath.

      The question is, what kind of idiot let a developer out without an (B) operator (FH) to tell him what to do?

      CAPTCHA: captive. Seriously, you can't make these up.

    51. Re:Version Control = Good by gweihir · · Score: 1

      If you do not use version-control on larger projects, then you are not a "developer", you are a hack. Sorry to be so blunt, but writing software professionally requires having some standards and version-control is non-optional.

      The same thing this poor amateur suffered would also have happened on a disk-crash, a stolen laptop, etc.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    52. Re: Version Control = Good by gweihir · · Score: 1

      If you do not push to remote with git then you have no clue what you are doing.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    53. Re:Version Control = Good by btroy · · Score: 1

      I totally agree with your statement. Please use version control and project control. I've seen something similar to that, someone surviving on self copies. However, I got bit by a bad backup policy at a company once. Because it was dev, they only kept 30 days of backups onsite and offsite. One of the admins accidentally dropped the project containing my code, yes software that was promoted to production. Thirty days later - no code.

      The only thing that saved my behind was the fact that I'd backed it to a a CD ROM right before prod. Thank goodness I didn't totally trust the system. We copied them back from "my backup" and I raised hell to the point they agreed to do aged backups for all open system projects.

      Another reason to do remote disconnected version control and backups - ransomware.

    54. Re: Version Control = Good by chipschap · · Score: 1

      Git is fine for single-person projects and certainly scales.

      But for what I do (write stories and novels), my 'projects' are single-user and typically single-file. Still, I *definitely* need version control for the "oops, I didn't want to delete that chapter" moments.

      For my purposes RCS is just fine. It's fast, lightweight, well-integrated with Emacs, more or less plain text, and has just enough features to be practical for what I'm doing. Laugh if you will at such an old system, but it still has its place.

      My working copy and RCS repo is of course backed up via rsync to a strongspace.com free account, and then replicated to multiple computers (desktop, laptops, netbook).

    55. Re:Version Control = Good by Anonymous Coward · · Score: 0

      This also about good OpSec. Why would you test a new piece of software on your production code.

    56. Re:Version Control = Good by gweihir · · Score: 1

      Using revision-control as backup is absolutely no problem if
      a) you mark backups as "backup"
      and
      b) your repository actually gets backed up

      Please stop giving bad advice.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    57. Re: Version Control = Good by Anonymous Coward · · Score: 0

      Linus called someone a moron for having that misunderstanding. Being able to use Git locally without a server is one of the core requirements he started with before creating Git.

      The problem was this guy didn't back-up his .git dir. There is no technical reason you have to push to a remote. It sounds like you're stuck in the bad old days before distributed source control systems.

    58. Re:Version Control = Good by Anonymous Coward · · Score: 0

      Meh. We've been bugging management that we need Version Control for the past year and a half and they won't budge. Fuck it. You know what happens if we lose the code? We can point to the email chain and say "We warned you". And then I get to rewrite all that code again, and get paid to do it.

      Also, it's probably the only way they'll let me refactor the code. "If it's in production, it's good!" :: shrug :: I'll absolutely rewrite the same goddamned thing for the rest of my life if the checks cash.

    59. Re:Version Control = Good by SecurityGuy · · Score: 1

      Even if that is just a repo on the same box.

      Nah, I disagree, it's all about backups. If I were that developer, I'd curse the software a bit, be annoyed that I have to restore 3 months of my work, kick off the restore, go make a cup of coffee and the restore would be done when I get back. His rant reads like he actually has to start over an redo 3 months of work.

      A repo on the same box saves you from accidental deletion. Backups save you from most possible mishaps, including user carelessness.

    60. Re:Version Control = Good by Anonymous Coward · · Score: 0

      What kind of idiot doesn't know you can delete file permanently in Windows? Is that Ctrl-Del or Alt-Del?

    61. Re: Version Control = Good by Anonymous Coward · · Score: 0

      And how would it magically erase a backup? You do have backups, right?

      Anyone who doesn't keep backups deserves zero sympathy. Hell, the guy in the article is so clueless that he doesn't even know how to undelete files. He may not have gotten them all back, but I bet he could have gotten the majority of them back. It's probably too late now, with the idiot continuing to use his computer and overwriting everything instead of shutting it down right away.

    62. Re: Version Control = Good by gweihir · · Score: 1

      Linux is talking about collaborative development. That is a different situation. As usual, some understanding required.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    63. Re:Version Control = Good by Anonymous Coward · · Score: 0

      It's literally a GUI wrapper over Git. It's as stable or buggy as Git is.

      lol.

      That's quite some Mandela effect right there... In the world I remember, wrappers, particularly on Windows, generally were themselves even buggier than what they were trying to wrap over...

    64. Re: Version Control = Good by Dishevel · · Score: 1

      Seems like you read about git one day and then decided that you understood what it is and all it can do and now have opened your mouth and been found a fool.

      --
      Why is it so hard to only have politicians for a few years, then have them go away?
    65. Re:Version Control = Good by Applehu+Akbar · · Score: 1

      What kind of developer doesn't do backups?

      Must...control...impulse...to...make...Windows...based...punchlines.

    66. Re:Version Control = Good by mrbester · · Score: 1

      It's a complete lack of understanding of any source control. He probably thought "oh, this has Git built in, okay, I've heard of that, I'll create an account" and then assumed magic pixie dust backup like Dropbox would keep his files under source control as he never did an initial commit. "But my files were there and I set up a repository! That's all I need to do and Microsoft fucked me!"

      --
      "Wait. Something's happening. It's opening up! My God, it's full of apricots!"
    67. Re:Version Control = Good by mrbester · · Score: 1

      Arguably he didn't use it then either and most likely has never used it.

      --
      "Wait. Something's happening. It's opening up! My God, it's full of apricots!"
    68. Re:Version Control = Good by Darinbob · · Score: 1

      Why is this bad advice? Having 10 "this is a backup" commit in the log to every 1 real commit confuses the teams and makes it much more difficult to get an overview up revision change history. Continuous builds means you should never commit unless the code can build cleanly and pass the regression tests. If someone is doing this then it should be in their own private branch and never on the mainline.

    69. Re: Version Control = Good by hackwrench · · Score: 1

      I use zip files and git. So does QB64.

    70. Re:Version Control = Good by modmans2ndcoming · · Score: 1

      How did he keep his job?

    71. Re: Version Control = Good by angel'o'sphere · · Score: 1

      Git is "the state of the art" version control system.
      For a single developer it does not really matter what he is using, however using "the state of the art" can hardly be a mistake.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    72. Re:Version Control = Good by hackwrench · · Score: 1

      Shift Del. I live in File Manager and use Shift Delete every day.

    73. Re: Version Control = Good by mikael · · Score: 1

      The hazard with git is that a "git pull" will overwrite uncomitted files that have been changed if someone upstream has changed those files.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    74. Re:Version Control = Good by mikael · · Score: 1

      I'd recommend an external USB hard disk drive of the same profile as your internal drive and with a cloned version of your Linux/Windows dual boot configuration. That's saved me during a power failure that temporarily whacked the drive (caused by a relative having several beers before starting some DIY). I could just slot out the old drive and pop in the external drive, fix the boot installer and continue working.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    75. Re:Version Control = Good by mikael · · Score: 1

      I briefly had to work with SourceSafe on a large team with 20+ developers. It was absolute chaos with the official workplace policy of backup everything as often as you can. The solution to the problem of "the application isn't running" was "try pulling the latest changes and do a rebuild".

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    76. Re:Version Control = Good by I'm+New+Around+Here · · Score: 1

      Hey! Lucky for you, I found about 90% of them.

      --
      If you think I voted for Trump because of this post, you're wrong. I voted for Dr. Jill Stein of the Green Party. Again.
    77. Re: Version Control = Good by Anonymous Coward · · Score: 0

      But fucking apps should not delete without a clear warning written clearly not just a "delete ABC ?" , Stupid coders especially ones not good in English , golly gosh, should not be writing the msg.

    78. Re:Version Control = Good by ChoGGi · · Score: 1

      This is why not playing with a new tool on the only copy of your existing code base is a good idea.

    79. Re: Version Control = Good by Anonymous Coward · · Score: 0

      Should have not shown the cd backup and asked for a massive bonus if you can retype the project in 1 hour. Then just copy the files back and profit.

    80. Re:Version Control = Good by Anonymous Coward · · Score: 0

      I'm sure I'm not the only one who learned about backups the hard way. For me it was deleting a months work on my PhD thesis, for this guy it was losing three months worth of coding. You swear, break things, get drunk, then work out a backup strategy (or two, or three) to make sure that shit never, ever happens again, and start over.

    81. Re:Version Control = Good by nullforce · · Score: 1

      The default for VS Code is git. (I see no indication that he used something else.) He "@jens1o I hadn't commited any of them to any repository." Seems pretty clear what discard changes would do. He would've royally fucked him self with git command line too.

    82. Re: Version Control = Good by aap · · Score: 1

      The easiest way to regularly back up your .git directory is by pushing to a remote... Even if it's on the same machine.

    83. Re: Version Control = Good by aap · · Score: 1

      Why is zip easier than git push?

    84. Re:Version Control = Good by nullforce · · Score: 1

      The default source control in VS Code is git. There's a reason this github is giving a 404 for that guy's account. He must've deleted it out of embarrassment.

    85. Re:Version Control = Good by Anonymous Coward · · Score: 0

      I think you just described the architecture of SVN.

    86. Re: Version Control = Good by Anonymous Coward · · Score: 0

      git pull -r should be your default reflex.

    87. Re:Version Control = Good by Anonymous Coward · · Score: 0

      For me it was deleting a months work on my PhD thesis ...

      Ouch! What happened then? Did you recover in time?

    88. Re:Version Control = Good by sls1j · · Score: 1

      I'm guessing that his 3 months of work would have been 3 days of work for an average programmer. On the bright side he's learned a lesson that he won't soon forget. And now he has that opportunity to refactor his code he's secretly been wanting to do anyway.

    89. Re: Version Control = Good by Anonymous Coward · · Score: 0

      My boss just deleted 15 years of my emails by changing the retention policy on the whole inbox (and folders) instead of deleted items. There may be a backup somewhere on a usb stick...

    90. Re: Version Control = Good by dougdonovan · · Score: 1

      you gotta cover your a** man. its the developers fault.

    91. Re:Version Control = Good by movdqa · · Score: 1

      Yup. 1 month of work that isn't in a repository? Or at least with multiple backups? I can't imagine.

    92. Re: Version Control = Good by movdqa · · Score: 1

      Might not even be a mistake. Disks die from time to time. You might get hit with a disaster (earthquake, flood, tornado, fire, electrical damage). Always have backups in multiple locations.

    93. Re:Version Control = Good by Anonymous Coward · · Score: 0

      No, he was using 'git' here which is not a Microsoft product. Visual Studio Code is, but both VSCode and Git were performing correctly without any bugs.

      The buttons he pressed did what they were supposed to do, he just didn't know what the buttons he was pressing did.

    94. Re: Version Control = Good by djinn6 · · Score: 1

      I put the zip and copy to cloud commands in a script, so it exactly the same as git push, but I don't need to spend time setting up a remote depot like git.

    95. Re:Version Control = Good by UnknownSoldier · · Score: 1

      ... and nothing of value will be lost.

    96. Re: Version Control = Good by Swave+An+deBwoner · · Score: 1

      Not if your boss finds it first.
      /s

    97. Re: Version Control = Good by sfcat · · Score: 1

      Git is "the state of the art" version control system. For a single developer it does not really matter what he is using, however using "the state of the art" can hardly be a mistake.

      Of course if you say its "the state of the art" then we must all use it for all possible uses then. Look kid, there are many revision control systems. For a single dev, almost all of them are better than git. You know what git is good for? Its good for large scale open source projects. Your team at work should probably be using perforce as its scaling issues with 1000s of devs likely wouldn't matter for your team of 8 (or whatever). Yet you still insist on using something that isn't really as good for day to day dev because its "state of the art". Have fun manually merging things constantly (perforce doesn't make you do this unless you actually made two conflicting modifications). In git, conflicts happen far too often. Also, since you probably rarely change your remote repo to which you are pushing code, you don't actually use the main advantage of git.

      Revision control is good but that doesn't mean you are an expert in different revision control systems, especially if you've only used 1 or 2 of them. Older devs will likely have seen 4 or 5 roll through at least and understand that newer isn't always better.

      Now get off my lawn...

      --
      "Those that start by burning books, will end by burning men."
    98. Re: Version Control = Good by PoopJuggler · · Score: 1

      Perforce. You will never look back.

    99. Re:Version Control = Good by Anonymous Coward · · Score: 0

      What kind of developer uses windows!?!

    100. Re:Version Control = Good by Anonymous Coward · · Score: 0

      What kind of developer uses windows...

    101. Re: Version Control = Good by Anonymous Coward · · Score: 0

      Dangerous defaults are an antipattern. While someone whos been on the block will always save alot and make offsite backups, I think unsafe defaults shouldnt be the norm. The dev expected more safety and files on disk to stay intact from as it was the initial state. Those expectations are reasonable defaults.

    102. Re: Version Control = Good by Anonymous Coward · · Score: 0

      Offsite backup plus multiple local copies is much more important. I never understood the fetish of stale code. Often a new go at it turns out better and simpler. I dont lose hours of work but prototype, iterate and weed out shit code.

    103. Re: Version Control = Good by Anonymous Coward · · Score: 0

      It sucks that you can't afford a personal laptop or NUC, much less a usb stick. Do you work with creamier?

      If you boss doesn't approve a license for VMWare or a free hyoerV or linux install, you are either terrible at your job or should change bosses.

    104. Re:Version Control = Good by Anonymous Coward · · Score: 0

      The same idiots that keep all their university work on one thumb drive, then it gets corrupted and they bring it to the desktop support people to "recover" when they could have been using the free 30GB Google Drive storage that comes with their free EDU Google accounts the University offered everyone, with their .edu Google email etc.

      In my case I managed to find a tool and recovered the files and they got lucky. I heard plenty of horror stories from others while I was working there about phd students losing 4 years of work because only one copy of it existed. Happens more than you think.

    105. Re: Version Control = Good by Anonymous Coward · · Score: 0

      Dangerous defaults are an antipattern.

      This is another reason I prefer Mercurial to Git.

    106. Re: Version Control = Good by Anonymous Coward · · Score: 0

      Maybe this is true with older git, but modern git will not let you pull if there are conflicts. It will fetch and then warn you instead of merging.

    107. Re:Version Control = Good by Anonymous Coward · · Score: 0

      what job? any workplace would have a revision control system in place.

    108. Re: Version Control = Good by Anonymous Coward · · Score: 0

      But fucking apps should not delete without a clear warning written clearly not just a "delete ABC ?"

      You mean like this?

    109. Re: Version Control = Good by Anonymous Coward · · Score: 0

      Conflicts happen rarely in git with the default settings. So rarely, that last week I merged an IC vendor's modified Linux kernel up through 40 kernel releases (over 1000 commits) to the latest upstream release in around half an hour and only had to deal with a handful of conflicts, mostly in makefiles where both the vendor and upstream had added new rules in the same location (and probably if I did this frequently enough I could configure git to automatically recognize and deal with such changes itself). Probably you are referring to what happens if you use git mergetool, which by default will normally give you a choice of a handful simple tools that show you all the changes in the conflicted file in 3-way merge style, but you can change the preferred mergetool to something better, even p4merge if you like, and many of those tools have an option to skip over the change blocks that can be automatically merged so you can focus on the real conflicts, you just have to read their manual and learn how to use them beyond the basic A/B/edit options.

    110. Re:Version Control = Good by Anonymous Coward · · Score: 0

      The version of SourceSafe I was exposed to didn't propagate deletions.

      Developer A would create a file, Developer B would refactor it into something better and delete the file, and Developer A would update, and it wouldn't delete the file. Developer A would then call functions in the file, and Developer B's code tree would stop compiling.

      Yay.

      Perforce had been purchased, but because it had an actual manual that you were expected to reference, nobody bothered -- one of the Microsoft-is-best-at-all-the-things developers "stood up" SourceSafe instead.

      Developer C got so tired of the whole mess, he'd check out the code, copy it to a working directory, and delete the checked out version. He's work on the code, and when ready to push, he'd check out the code again, blindly copy all of his files over top of the repo, and commit.

      One weekend, the working version of the source repository was stood up in Perforce, the SourceSafe repo was archived and deleted, and then an email was sent to all of the developers telling them how to check out their code, and what the expected workflow was supposed to be.

      Developer C shrugged and did his usual thing⦠to find his changes rolled back wholesale. He stormed off to the team lead to complain⦠and then asked (somewhat contritely) for help with the "new" process.

    111. Re: Version Control = Good by Anonymous Coward · · Score: 0

      The best way of making a backup with git is to push to a remote.

      cd /media/usb
      git init --bare backup
      cd ~/workspace
      git remote add backup /media/usb/backup
      git push --all backup

      Even better is that this method easily allows you to switch to offsite backups just by setting up a github account and

      git remote set-url backup https://github.com/myaccount/backup.git

    112. Re:Version Control = Good by Z00L00K · · Score: 1

      Which indicates that the wrapper he used was bad from a user interaction perspective lacking important warnings.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    113. Re:Version Control = Good by Anonymous Coward · · Score: 0

      What kind of developer doesn't know how to undelete all files in a specific folder? Give me Norton Disk Editor and an admin privilege and I would manually undelete your project files. Never mind the Disk Editor, I can use debug.exe which is included in all Windows OS.

    114. Re:Version Control = Good by Anonymous Coward · · Score: 0

      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.

      Put their hands around his neck and squeezed hard? Isn't that how it is usually done?

    115. Re: Version Control = Good by Just+Some+Guy · · Score: 4, Informative
      That's not true:

      # Create an empty git repo.
      $ cd /tmp && git init --bare repo.git
      Initialized empty Git repository in /private/tmp/repo.git/

      # Clone it.
      $ git clone repo.git test_dir && cd test_dir
      Cloning into 'test_dir'...
      warning: You appear to have cloned an empty repository.
      done.

      # Create a file and add it to the repo.
      $ echo foo > foo && git add foo && git commit -m 'Added foo'
      [master (root-commit) 1813607] Added foo
      1 file changed, 1 insertion(+)
      create mode 100644 foo

      # Modify that file and add the change to the repo.
      $ echo foo2 >> foo && git add foo && git commit -m 'Modified foo'
      [master 6cb6f22] Modified foo
      1 file changed, 1 insertion(+)

      $ cat foo
      foo
      foo2

      # Push the change to the repo we made earlier.
      $ git push
      Counting objects: 6, done.
      Delta compression using up to 8 threads.
      Compressing objects: 100% (2/2), done.
      Writing objects: 100% (6/6), 421 bytes | 421.00 KiB/s, done.
      Total 6 (delta 0), reused 0 (delta 0)
      To /tmp/repo.git
      * [new branch] master -> master

      # Go back to the first version of foo. This simulates the case where
      # we pushed the first commit, then someone else added the second
      # commit.
      $ git reset --hard HEAD^1
      HEAD is now at 241f76f Added foo

      # Now change that file in a different way.
      $ echo foo3 >> foo

      # See? It's different from that second commit.
      $ cat foo
      foo
      foo3

      # Try to pull in that second commit that would overwrite the
      # uncommitted change we just made. Git has your back.
      $ git pull
      Updating 241f76f..3a175e4
      error: Your local changes to the following files would be overwritten by merge:
      foo
      Please commit your changes or stash them before you merge.
      Aborting

      --
      Dewey, what part of this looks like authorities should be involved?
    116. Re:Version Control = Good by Anonymous Coward · · Score: 0

      How about the recover.exe utility bundled with Windows since WinNT up to Windows 10 to undelete his files.

    117. Re: Version Control = Good by Just+Some+Guy · · Score: 2

      Your team at work should probably be using perforce

      LOL. There's no compelling reason why I'd use a proprietary version control system for anything trivial or important. If nothing else, none of them have ecosystems that hold a candle to git. Every editor supports it. Every build system supports it. Every CI/CD pipeline supports it. Every ops tool supports it. 95% of open source packages are hosted in it.

      Feel free to use whatever you want, of course, as long as you understand that what you're giving up by not playing in the Git ecosystem is unlikely to make up for any perceived advantages over Git.

      --
      Dewey, what part of this looks like authorities should be involved?
    118. Re:Version Control = Good by Anonymous Coward · · Score: 0

      That sounds suspiciously like he had used sourcesafe. That sucker can wipe your whole db very quickly. That is why he didnt trust it. Plus the 'locking'. Which is kind of convenient in particular workflows. Most people use merging/rebase these days though as we do tend to like to work on the same files. In some projects it is not an issue. But in some it is a massive pain.

    119. Re:Version Control = Good by 91degrees · · Score: 1

      It isn't enough to commit the code, you also have to push it somewhere. Even if that is just a repo on the same box.

      Still a risk here though. PCs can get stolen, or infected with viruses, or destroyed in a fire.

    120. Re: Version Control = Good by Anonymous Coward · · Score: 0

      Zfs with snapshots. Solved my problems for good.

    121. Re: Version Control = Good by Man+On+Pink+Corner · · Score: 1

      To be fair to the developer, "Do you want to discard all changes?" is not even remotely the same question as "Do you want to delete all files?"

      That's no excuse for not keeping backups, of course. Everybody who has used a computer for more than a few days has probably had to learn the same lesson the hard way. Nothing to do but move on with life. The code was probably full of bugs anyway.

      You step into the river, but the water has moved on
      Your data is no more

    122. Re: Version Control = Good by Anonymous Coward · · Score: 0

      Or say, "shit, going to take me at least 3 months to redo it" and then just slack it.

    123. Re:Version Control = Good by Anonymous Coward · · Score: 0

      I had to rerun a small number of experiments and rewrite some. Took about a fortnight of long days to roughly catch up. Lucky it was mid thesis and not end of.

    124. Re:Version Control = Good by Anonymous Coward · · Score: 0

      "And then I get to rewrite all that code again, and get paid to do it."

      Bonus points for implementing your own secret backup system, making the rewrite a lot easier for you!

    125. Re: Version Control = Good by Jesus+H+Rolle · · Score: 1

      administrate

      I'd like to conversate with you about your butching of English.

    126. Re:Version Control = Good by Gussington · · Score: 5, Insightful

      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 developer doesn't even know that when Windows deletes a file, the file is still there, only the index is deleted, any data recovery util will get it back.
      It would've taken less time to recover the deleted files than rant about it on the Internet...

    127. Re:Version Control = Good by gweihir · · Score: 1

      And why do you assume that this is a shared repository and why do you assume continuous builds? Perhaps you think you way is the only right one to do it? If so, there is a rather serious problem on your side.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    128. Re:Version Control = Good by Anonymous Coward · · Score: 0

      True, but he is listed as CEO! lol

    129. Re: Version Control = Good by Anonymous Coward · · Score: 0

      Frankly, you could at least use a user-friendly VCS if your project is single-developer and you have a free choice in version control.

      Bazaar is what I use for my local version control. No need for a server or anything. (Yes, I'm aware that git doesn't need one either.)

      cd ~/project
      bzr init
      bzr add .
      bzr status
      bzr commit -m "imported project"

    130. Re: Version Control = Good by Anonymous Coward · · Score: 1

      as elsewhere in life: belt, suspenders, and duct tape

    131. Re: Version Control = Good by macsuibhne · · Score: 1

      Also, free for personal use and platform agnostic.

      Tony.

      --
      -- "Quis custodiet ipsos custodes?" -- Juvenal
    132. Re:Version Control = Good by gravewax · · Score: 1

      No bug, VS Code uses git. If you tell git to discard your changes it does. for him his changes were everything as he was a retard and never commited anything then used tools he didn't understand and ignored warnings without understanding the consequences. nothing to see here apart from a developer (I use that word loosely) that you should put on your list of "do not hire this retard"

    133. Re: Version Control = Good by F.Ultra · · Score: 1

      You just ignored that I wrote that it was 15 years ago?

    134. Re: Version Control = Good by Anonymous Coward · · Score: 0

      Why would you not push toba remote? This is the purpose of git. A least make a daily copy to a USB stick, remote storage or some place other than your local machine.

      Keeping only one copy of your code, is a noob mistake. Should not be called a developer.

    135. Re: Version Control = Good by arglebargle_xiv · · Score: 1

      If you do not push to remote with git then you have no clue what you are doing.

      His cluelessness goes well beyond that, three full months of uncommitted work and no backups, he was one glitch away from losing it, failed hard drive, malware, anything. The only thing I'd take away from this is "don't hire this guy as a developer".

    136. Re: Version Control = Good by arglebargle_xiv · · Score: 1

      I use a remote bitbucket

      I dump my backups in a local bitbucket, copying files there is so quick the backups complete in next to no time. I didn't know there was a remote version of /dev/null. Wouldn't the network overhead of backing up up to that kind of kill you?

    137. Re: Version Control = Good by Anonymous Coward · · Score: 0

      No it doesn't you fucking ignorant.

    138. Re:Version Control = Good by Anonymous Coward · · Score: 0

      I would not call him an idiot, as only smart people learn from mistakes of others, but most of us need to make that mistake at least once. ;)

    139. Re:Version Control = Good by Anonymous Coward · · Score: 0

      Well, I can relate to that, in the sense, that I was working in a company, that had an unfortunate accident, where source server crashed and it did not had backups(it was long long time ago, though and why they did not have backup still baffles me), but ... I assume, that work pays for my time spent on coding and it is responsibility of company to look after control system server and if submited code is safe there. It is easier to write code anew, than think how to do it.

      You haven't had a bad experiences with person, who was working on the same file. I would not like to work on the same file as well, because if I'm adding some code, that is using already established function in this code and someone comes along and instead of adding new version of function, fucks up old one and on top of that it is not working anymore... it means, that in the end I have to spend time to fix this person's *work*, that is not done properly... I'd rather lock file, than consider strangling someone - it is just for safety of others.

    140. Re: Version Control = Good by Anonymous Coward · · Score: 0

      It seems "discard all changes" means discard all changes since the last commit. He never made a commit. Hence all his files were deleted.

    141. Re: Version Control = Good by SuperDre · · Score: 1

      Well, i can imagine his fear for merging, as i have already heard/seen a lot of problems with it with a lot of people. Best is to avoid needing to merge.

    142. Re: Version Control = Good by angel'o'sphere · · Score: 1

      Look kid, there are many revision control systems. For a single dev, almost all of them are better than git. You know what git is good for? Its good for large scale open source projects.
      Actually you are bad in reading. For a single person the VC system is irrelevant
      Because all the things you mention later don't happen.
      And yes, exactly because it is irrelevant it is better to use git, because most likely your next project will be using git and nor perforce or bitbucket, or MKS, or what ever.
      Why would a single person use SVN? When Git is already preinstalled? Why would it use CVS or RCS? (RCS is even no longer preinstalled on most unix/linux distroes).

      Git with SourceTree or the IntelliJ pluggin is just wonderfull for day to day work. Perhaps you should educate yourself about good git workflows?

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    143. Re:Version Control = Good by modmans2ndcoming · · Score: 1

      The guy that is so unproductive and chaotic that he causes headaches for anyone else working there.....Did you not read the comment I replied to?

    144. Re:Version Control = Good by Anonymous Coward · · Score: 0

      On the other hand . .
      I can't click on an excel hyperlink cell to launch a home video without a warning. IMO, Microsoft developers don't use their own s/w nor do they employ "knowledgeable" testers.

    145. Re:Version Control = Good by marko123 · · Score: 1

      Novel writer myself. Losing words sucks. But it might be good practise for making the cuts you need to :) All the best.

      --
      http://pcblues.com - Digits and Wood
    146. Re:Version Control = Good by Anonymous Coward · · Score: 1

      The free version of Recuva helped us out when a vindictive former employee wiped all his work files from his company issued computer. You do have to do it asap before the space is written over.

    147. Re:Version Control = Good by Aighearach · · Score: 1

      Sure. Do both. But if you can't tell them apart and tell which one does which, you won't know what protection you even have, and won't be able to plan it well. He's not at the stage of getting a lot of it right and needing to cover the edge cases; he needs the basics, the "why version control" not just the security/safety checklist.

    148. Re: Version Control = Good by Dog-Cow · · Score: 1

      Funny. It's never done that for me.

    149. Re:Version Control = Good by shutdown+-p+now · · Score: 1

      If that's what you understand, then you haven't bothered reading the story. He was using Git.

    150. Re: Version Control = Good by Anonymous Coward · · Score: 0

      It's a minor inconvenience but you act like they murdered your family. Just restore from backup. It takes all of ten minutes.

    151. Re: Version Control = Good by gweihir · · Score: 1

      Indeed. And it is not only the insane risk he took, it is his complete lack of understanding how things work. And then blaming others for his screw-up.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    152. Re:Version Control = Good by Anonymous Coward · · Score: 0

      Assuming Visual Basic source code is a flat text file without the .txt extension... it makes data recovery difficult.... especially for thousands of individual files. Likely he'd be able to get the lions share of them back, but not everything. Anything beyond basic "looking for deleted files" involves scanning the surface of the entire disk looking for a file header, which txt files don't have.

    153. Re:Version Control = Good by Anonymous Coward · · Score: 0

      I am that developer.

      Work with Clearcase/RTC, then we can discuss how reliable this "source control" really is.

      The first time I got my code "merged" by this awful tool, that was the last time I didn't zip the folder before touching that sh*t.

      These days I always ask "which source control system are you using?" during the interview, if its clearcase then I'm out of there.

      Nice project management tool though, but terrible source control. I especially like how the server locks up every once in a while and needs a reboot!

    154. Re:Version Control = Good by Anonymous Coward · · Score: 0

      The same diploma-mill hindu-chimp-coder imported on H1B from shitty jungle to develop Winblows.

    155. Re: Version Control = Good by Anonymous Coward · · Score: 0

      It also fails to open if your server setting is wrong.
      Also webstorm has an additional local repository that auto commits large changes like this, it's saved me only a few times but I wish the auto commits was more wide spread. Windows disables shadow copies by default but here is a script to run as a task to shadow copy your drive using PowerShell. No other way to do it. Sometimes I think Microsoft is just like every other big corporation, too many projects to really know what is important https://stackoverflow.com/questions/14207788/accessing-volume-shadow-copy-vss-snapshots-from-powershell

    156. Re: Version Control = Good by Pieroxy · · Score: 1

      There is no need for a disaster for a disk to fail. Disks fail. It happens.

    157. Re:Version Control = Good by Anonymous Coward · · Score: 0

      What kind of developer assumes that when specific "source repository" software deletes files, it does it in the same way as when a user selects a file and deletes it in Windows Explorer?

      Oh right, a Slashdot commenter...

    158. Re: Version Control = Good by tk77 · · Score: 1

      I'm not arguing, if Bazaar is better in ways then git for a single developer then thats fine. Choice is good. However git's version of your example is exactly the same:


      cd ~/project
      git init
      git add .
      git status
      git commit -m "imported project"

    159. Re:Version Control = Good by Anonymous Coward · · Score: 0

      Full disclosure: I once lost almost 10,000 words of a novel I was writing due to my own cluelessness about certain backup systems. It was a hard lesson.

      Slashdot can help you out. I'll get you started:

      "It was a dark and stormy night."

      Only 9993 words to go!

    160. Re:Version Control = Good by Aighearach · · Score: 1

      You're basically arguing with step 2 because you think step 3 is more important. Your only point is that you didn't understand what I said. Backups are a separate thing, yes I agree that also is important, and it also could have saved him. But if he followed all the best practices, he would not have been restoring a backup, he'd have just checked out his code again.

    161. Re:Version Control = Good by RubberDogBone · · Score: 1

      Same things happened at my last IT job, where SourceSafe (and a very old version of it, at that) was the standard.

      But it wasn't helped any by a QA process that exempted half the work, because the testers had no training on doing QA for what we coded, and had no way to test them anyway. QA would either rubberstamp changes OR refuse to touch the change requests which were always driven by customer deadlines.

      Can't even remember how many times we pushed to prod on our own, or did other tricks to make the new code hit prod while we waited for QA to stop holding their breath and turning blue in protest.

      QA: "Hey you guys are trying to push an update to Prod but we already see the file is the same in Prod and SourceSafe. Is your change request paperwork wrong?"
      (devs scrambling to back changes out of live prod)
      Devs: "Oh, hey, haha, just do a refresh, sometimes it sticks you know, haha. That'll clear it!"
      QA: "Oh yeah it's fine now. We're pushing your changes to Prod."

      Yes dev had access to Prod. My team was the only group in the company that even worked on that code and nobody else could code it or test it or do QA on it, so we had to do all our own dev, AND ProdTest it AND sandvbox test it and stage it and so forth, do paperwork to send it to QA, so QA could say they had seen the paperwork and do a rudimentary file compare, and then WE would push the updates into Prod ourselves.

      The company was working to migrate all this stuff to VB, a platform they supported within the QA process. Our product was MUCH better and vastly more sophisticated. One example as document rendering: their product could not print on both sides of a sheet of paper, where ours was totally configurable. And no you could not do this in the print dialog because the end output needed to have some pages with one side and some with two and switch back and forth depending on various rules. We could do that. The other system was stuck on single side. But idiots could code for it. And that meant they could get interns to code for it and let QA debug it when it didn't work. They didn't need any of the people on my team or what it cost to keep us. For clients, they would simply push selling the simple, dumb system as being cheaper and convince clients they didn't need to do mixed side printing or other neat tricks we could do.

      --
      Sig for hire.
  2. Guy made a mistake by DogDude · · Score: 1, Funny

    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.
    1. Re: Guy made a mistake by Anonymous Coward · · Score: 0

      The hard drive wasn't destroyed with a hammer, so no.

    2. Re:Guy made a mistake by Jiro · · Score: 4, Insightful

      Just because the user could have navigated the confusing user interface doesn't mean it's his fault. Microsoft created the user interface.

      By your reasoning there is never any such a thing as a user interface problem because the user could always have done something else.

    3. Re:Guy made a mistake by ShanghaiBill · · Score: 4, Insightful

      ... and it's Microsoft's fault?

      Yes, it is partly Microsoft's fault. Tools should be designed assuming users will sometimes do dumb things, or sometimes accidentally click the wrong button.

      This guy is clearly a moron, but there are a lot of morons out there, and software should be designed with that in mind.

    4. Re:Guy made a mistake by MightyYar · · Score: 5, Insightful

      There may very well be a user interface problem with the product. I don't want to blame the victim.

      However, this guy was going to lose his work someday. Maybe it would be a hard drive failure. Maybe a corruption. House fire. Who knows? The point is eventually he was going to have data loss because he doesn't back up. Microsoft may very well be the direct cause here, but this guy was NOT following any kind of best practices.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    5. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      yeah totally, which is why this is happening to developers all across the world as i type!

      you caught the sarcasm right?

    6. Re:Guy made a mistake by TWX · · Score: 5, Insightful

      I'd agree with this, especially in the context of the way Microsoft has trained users into normally expecting prompts when actions have very serious, arguably permanent results. User bears some responsibility, but when the design mentality of the UI since the beginning of the company has been to use confirmation prompts then there's an expectation that this will continue.

      If I were him I'd immediately boot to some utility that scans the disk for filesystem clusters marked as deleted/available to attempt to undelete them. That is still a thing, right?

      --
      Do not look into laser with remaining eye.
    7. Re: Guy made a mistake by Anonymous Coward · · Score: 1

      What difference, at this point, does it make?

    8. Re:Guy made a mistake by Miamicanes · · Score: 1

      I think his main complaint is that it did something that has permanent & profound consequences without making it abundantly clear that he was asking it to DO something with permanent and profound consequences.

      I might be wrong, but I'm pretty sure the standard git client and library (used by almost everyone, including Windows) intentionally has NO WAY to literally purge files AND THEIR HISTORY from an existing repo "in place". If you have some need to rewrite history and physically purge all evidence that some file ever existed from the repo, you have to clone the repo with a filter that omits those files, so you'll end up with TWO local copies of the repo... the old one, with everything intact, and the new one, with rewritten history.

    9. Re:Guy made a mistake by vux984 · · Score: 1

      Just because the user could have navigated the confusing user interface doesn't mean it's his fault. Microsoft created the user interface.

      It's his fault because he had '3 months work' with no backup, not a proper offsite incremental backup, not even a zipped copy in another folder, not even using source control.

      That's indefensible right there.

      That he then took this highly valuable data, of which he had no backups, and decided to play with it with a tool he was unfamiliar with.

      That's just reckless.

      It sucks that he lost his data. It really does. I've been there. I feel for the guy. But It doesn't matter how you spin it the lesson here is not that Visual Studio Code is dangerous -- the lesson here is: MAKE REGULAR BACKUPS.

      By your reasoning there is never any such a thing as a user interface problem because the user could always have done something else.

      No. We can have a conversation about user interface problems, and I readily agree that Visual Studio code has some. But the reason he lost his data is not a user interface problem in Visual Studio Code. The reason he lost his data is because he didn't make backups.

    10. Re: Guy made a mistake by mpercy · · Score: 1

      No, it was wiped...Like with a cloth or something?

    11. Re: Guy made a mistake by Anonymous Coward · · Score: 0

      You're gonna need a bigger cloth.

    12. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      His hard drive could have crashed and burn. He'd still lose 3 months of code. Should he then blame the hard drive manufacturer?

    13. Re:Guy made a mistake by Nemyst · · Score: 4, Informative

      I'll agree that the language could be clearer, but it does show this popup when you try doing this right now. That should be a hint that something bad might happen, I'd say.

    14. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      To be clear, there is a warning dialogue that pops up warning you that the changes are permanent. He ignored it.

    15. Re:Guy made a mistake by F.Ultra · · Score: 1

      Actually thinking about it all things with a computer is crazy insane interface wise. I.e why is the power cable so easily to pull out when VGA, Serial and Parallel cables was screwed to the motherboard?

      I know of one instance back in the 80:s when a company switched from typewrites to computers and after a person had written some text and closed the word processor and "do you want to save the document?" appeared he clicked "no" because he thought that it wanted to create a copy since logically the text was stored since he had written it. We today might think that he was stupid but I think that he was right and it's we that are stupid. Why wouldn't a modern computer simply store each and every change to a document automatically?!

      The same with this guy, why are files deleted and not always under version control. They could still be counted as free storage and it's location could be recycled if the real free storage is insufficient once he does a save of a new file.

      There is really no reason why you shouldn't be able to write in a document, experience a power outage, boot the computer, load the document and be able to continue right where you left of, including full undo support back to the first edit to the document.

    16. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      too bad 99% of Slashdot readers aren't going to see your comment.

    17. Re:Guy made a mistake by TiggertheMad · · Score: 1

      This guy is clearly a moron, but there are a lot of morons out there, and software should be designed with that in mind.

      "When you make your code moron proof, they just build better morons..." - Tigger the Mad's axiom of programming #4

      --

      HA! I just wasted some of your bandwidth with a frivolous sig!
    18. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      Yes, it is partly Microsoft's fault. Tools should be designed assuming users will sometimes do dumb things, or sometimes accidentally click the wrong button.This guy is clearly a moron, but there are a lot of morons out there, and software should be designed with that in mind.

      Well, Microsoft's editor prevented that this moron's code got released in the wild, perhaps it is working as intended.

    19. Re:Guy made a mistake by JohnFen · · Score: 1

      Just because the user could have navigated the confusing user interface doesn't mean it's his fault.

      True. It's his fault for not having backups. I backup my work several times each day -- you never know when your dev machine is going to get hit by a meteorite or randomly burst into flames.

      Yes, Microsoft's UI should not have allowed this mistake to happen so easily. So, bad on them for that.

      However, not having backups? And especially trying out new software on your production code without making a copy of it first? That's just insanely stupid, and yes, entirely his fault.

    20. Re:Guy made a mistake by JohnFen · · Score: 1

      Except that, in theory, this guy isn't a naive computer user. He's a developer. He should be familiar enough with how computers work in the real world to know that you absolutely have to back your stuff up, and you can't trust them unconditionally.

    21. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      You can't design a tool against the user blatantly ignoring all warnings and doing stupid shit.
      Sometimes you want to delete a file.
      This requires the possibility of deleting files. No matter how many warnings you put up, someone who clicks through them all will delete his shit.
      Also, correct me if I'm wrong, but as far as I know the recycle bin only keeps files you manually delete through explorer.
      Not files deleted by other tools, such as git, par, etc.

    22. Re:Guy made a mistake by JohnFen · · Score: 1

      Yes, it is partly Microsoft's fault.

      I agree. Microsoft clearly violated a fundamental rule of UI (that is getting more and more ignored as the years go by):

      Every action a user can take should be undo-able.

    23. Re:Guy made a mistake by apoc.famine · · Score: 1

      Most of the time I'd agree, but we really don't need more morons writing code. I think this darwinian pressure on developers is a good thing for everyone. Hopefully he is forced to choose another career path after this.

      --
      Velociraptor = Distiraptor / Timeraptor
    24. Re:Guy made a mistake by F.Ultra · · Score: 1

      Of course, I was just ranting about the complete disaster that is computer interfaces regardless of operating system or vendor.

    25. Re:Guy made a mistake by atikare · · Score: 1

      though I agree it was a colossally stupid mistake on his part to not do backups for such a long period of time. seriously WTF! But even assuming reasonable timely backups of the frequency of say a week, losing a weeks worth of work is still horrible for the rest of [semi-reasonable] us. I am no willing to let MS off the hook for such pathetic UX screwup. Hell even losing a days worth of work in the middle of some critical firefight week can have serious consequences. its not reasonable to assume a BUYER BEWARE attitude with something as basic & solidified as version control. So the FU Microsoft is warranted. Now had it been a plugin from some 3rd party then its completely on you Not the editor.

    26. Re:Guy made a mistake by skids · · Score: 1

      he thought that it wanted to create a copy since logically the text was stored since he had written it

      Umm.. why would he expect a program to pester a user to make an extra copy of a document when the user tells it to quit? I cannot think of a good reason why a program would do that... If he thought software UI designers just sucked when they wrote that in, then why would he have trusted the program to save automatically? It should have set off some bells.

      As to why do a lot of editors not keep up to the minute autosaves... mostly because they are writing 5 API layers above the OS operation to actually flush content to disk, and at least 4 of those API layers suck balls.

    27. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      There was no "existing" repo. There was no history to delete. (unless I misunderstand the whole thing).
      What he effectively did was git status; git reset --hard

    28. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      Discarding changes or erasing all files? No, that doesn't sound like the same.
      Or, he didn't commit anything earlier? Then, he is a moron.

    29. Re:Guy made a mistake by Billly+Gates · · Score: 1

      There may very well be a user interface problem with the product. I don't want to blame the victim.

      However, this guy was going to lose his work someday. Maybe it would be a hard drive failure. Maybe a corruption. House fire. Who knows? The point is eventually he was going to have data loss because he doesn't back up. Microsoft may very well be the direct cause here, but this guy was NOT following any kind of best practices.

      I bet if he replaced Microsoft Code with Emacs or Vi this story would be marked as flamebait and not posted. But since it is from Microsoft it got posted as this is Slashdot.

      I agree and tell my colleagues now to avoid slashdot for non biased opinions sadly. It is quite ridiculous

    30. Re:Guy made a mistake by sverdlichenko · · Score: 1

      There is no such thing a data loss problem because user could always make backups.

    31. Re:Guy made a mistake by vux984 · · Score: 1

      "I am no willing to let MS off the hook for such pathetic UX screwup."

      Let's look at what he actually did. I've got visual studio code... I'm looking at it; and I think i see what he did.

      He created a folder for his project. He worked on it for 3 months. No backups, no source control. That's brain dead.

      He tries out Visual Studio Code. I suspect he doesn't even really know how git works at all; and decides to just start playing with its source control features without knowing what he's doing.... on his 3 months of live irreplaceable data. That's brain dead squared.

      He can't do anything with source control without a repo, so step one he has to initialize a repository. (essentially git init). No problem. Visual Studio code has an 'initialize repository' command.

      So now he's got an empty repository, and his working directory has 3 months of worth of new/changed files. In git parlance he's got 5000 items or whatever to be staged and committed with the next commit.

      He decides not go through with that which is fine.

      Disastrously though, he now selects 'discard all changes' for the project. This is again, git talk -- it dumps everything in the working folder since the last commit; or alternatively it restores you to where your last commit left you. Developers do this all the time on purpose. We do it to individual files all the time, and to working folders as needed.

      When you select it in Visual Studio code it prompts: "Are you sure you want to discard all changes? This is IRREVERSIBLE!" (caps is as seen in the actual warning dialog box).

      He clicks yes. Git restores the working directory to the last commit. In his case, though there is no last commit. Everything in his working folder is 'changes since the last commit' so it restores him to a blank slate. That's what discard all changes does in the context of source control. Its unfortunate he didn't know that. It's unfortunate the "IRREVERSIBLE" warning went unheeded. Its absurd that he was doing this on his live project rather than making a test project for... or a copy of his project folder to play with.

      He throws a temper tantrum on the internet because he decided to learn how source control worked on a live project with no backups and didn't know what he was doing.

    32. Re:Guy made a mistake by mrbester · · Score: 1

      He was in the source code management section where you manage source code (and you click on the Git logo to get there, it even has a tooltip on the icon). If that's confusing then God knows what his code looked like.

      --
      "Wait. Something's happening. It's opening up! My God, it's full of apricots!"
    33. Re:Guy made a mistake by angel'o'sphere · · Score: 1

      There is really no reason why you shouldn't be able to write in a document, experience a power outage, boot the computer, load the document and be able to continue right where you left of, including full undo support back to the first edit to the document.

      Erm, in what SF world do you live?
      With current memory and HD/SSD architecture this is impossible.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    34. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      idk, when a prompt pops up with the word IRREVERSIBLE in it, I stop and question why. Mebbe a RTFM moment, as distasteful as that is. Mebbe do a quick backup of my stuff before I go click OK to the message with that IRREVERSIBLE bit in it. Go grab a cup of coffee. Something. That's what a "professional" does.

    35. Re:Guy made a mistake by david_thornley · · Score: 1

      My personal stuff is done in my Dropbox account. When I have connectivity, which is most of the time, I have almost instant backups. I don't see why something like this can't exist for work environments. Instead, it's typically a matter of workstation drives not being backed up, and you have to remember to copy something to a shared drive somewhere if you don't want to lose it, and even then you can lose a day or week of stuff.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    36. Re:Guy made a mistake by Kaenneth · · Score: 1

      MS was just protecting the world from his code.

    37. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      It does tell you in a confirmation promt "Are you sure you want to discard ALL changes? This is IRREVERSIBLE!", he even says later on that he read the prompt. The problem is that he apparently did understand that discard means to delete pending changes, and since he never made a commit in the first place it deleted everything as it should.

    38. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      Undelete tools are still a thing unless you've upgraded to SSDs. However scanning a 1TB hard drive to recover file fragments takes forever and you get so many files you'd never have time to search thought them for that important document. Best use an undelete tool the instant you've deleted them so you don't have to do a full drive scan.

    39. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      If you never commit any files and then ask the version control system to restore your initial repo, they will all delete your current files (a few will rename your current files instead of deleting them). The guy never committed anything so he didn't have a history to fall back on. So you're not wrong, but you have mistakenly assumed he actually knew how to use a version control systems.

      For stories like these, It's really easy to see who reads the articles or other comments before posting.

    40. Re: Guy made a mistake by Anonymous Coward · · Score: 0

      The far future of at least as far back as 2011 when btrfs and minutely snapshots was a viable option if needed. Far further back if you use zfs and had money.

    41. Re: Guy made a mistake by Anonymous Coward · · Score: 0

      Exactly. All critical company data is, by policy, stored on an IT managed server. IT manages the backups for those servers which the company has defined as critical and needing backups and budgeted accordingly.

      If it is not on the company owned, IT managed, fully budgeted backup server, then it is either not critical or you violated company policy by not storing it there.

    42. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      As I've mentioned elsewhere in this thread, *Git* is the default version control system (VCS) for Visual Studio Code (as in most of the other non-'enterprise' Visual Studio clients these days). Since you appear to not be aware of this, Git is far from a Microsoft product -- it was conceived by Linus Torvalds as a better VCS to replace what they had been using to manage the Linux kernel.

      So this person didn't know how to use Git, and didn't realize that "discard pending changes", actually discards, well, pending changes. If you've never checked anything in, then everything you have in your folder is a pending change. So don't discard them! (As other people have remarked, that's why there's a big warning dialog box that says, "This is IRREVERSIBLE!")

      Look, I feel bad for the person who lost some work. But Git, even though it's the world's most popular VCS, is a power tool. And as Linux people will tell you, you shouldn't attempt to use power tools (even through Visual Studio Code) without Reading The Friendly Manual.

    43. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      Again, as a number of us have mentioned elsewhere in this thread, *Git* is the default version control system (VCS) for Visual Studio Code (as in most of the other non-'enterprise' Visual Studio clients these days). Maybe you hadn't heard that before, but you probably know that Git is far from a Microsoft product -- it was conceived by Linus Torvalds as a better VCS to replace what they had been using to manage the Linux kernel.

      As in many other Git clients, "discard pending changes", actually discards, well, pending changes. If you've never checked anything in, then everything you have in your folder is a pending change. So don't discard them! As other people have remarked, that's why there's a big warning dialog box that says, "This is IRREVERSIBLE!"

      So it's not really "Microsoft's UI" that "allowed this mistake to happen so easily." Again, as I said elsewhere, if you click on a warning like that, without thinking for a moment about what files were in the window you were just looking at, then I feel sorry for you. That was a terrible accident, and I hope it doesn't happen again; maybe next time pay closer attention?

    44. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      Like I've mentioned many times elsewhere in this thread, *Git* is the default version control system (VCS) for Visual Studio Code (as in most of the other non-'enterprise' Visual Studio clients these days). Maybe you hadn't heard that before, but you probably know that Git is far from a Microsoft product -- it was conceived by Linus Torvalds as a better VCS to replace what they had been using to manage the Linux kernel.

      As in many other Git clients, "discard pending changes", actually discards, well, pending changes. If you've never checked anything in, then everything you have in your folder is a pending change. So don't discard them! As other people have remarked, that's why there's a big warning dialog box that says, "This is IRREVERSIBLE!"

      So, no, it's not really "partly Microsoft's fault". Would you prefer they build a completely different Git client that does something different than all the others do when you click "discard"?!

      [See, now that sounds like something Microsoft would have done in the late '90s, though :) ]

    45. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      Here is my take on this issue as I fell into the same trap when I started using VS Code the first time. In my case it was a day's work and luckily I did not lose much. But as a developer for 20+ years, I use source control all the time,. But the VS team really need to take note and here is why.

      When you click on the source code control icon the first time you add code to a new repository or copy files from somewhere into a new git repository, all the files are UNTRACKED. Now, as a new tool user you click on the icons and this one says Discard All Changes (Yes or No) .
      Since there are "no Changes " as I have yet to checkin any of the files, in my mind it did not mater whether I say Yes or No. But if the user clicks Yes on Untracked files, POOF it is gone. All I am saying is, come on I love VS Code and some coool stuf in there. So how difficult it is to says, that there are Untracked files which will get deleted or if all the files areUNTRACKED show a different message. Bettter still DISABLE the damn discard button if all files are UNTRACKED.

      Yes 3 months no backup is bad, but the issue is still valid on VS Code.

    46. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      Agreed, I wonder if he even tried "previous versions" at the FS level... He may still have something to restore back to without knowing it.

    47. Re:Guy made a mistake by F.Ultra · · Score: 1

      Because the old tech (i.e the typewrites) worked that way, you typed and your work was 'stored'. His problem was that he thought that new tech (i.e a computer) would be like the old tech but better. Naturally he was wrong, which should be telling about how bad computers actually are.

    48. Re:Guy made a mistake by F.Ultra · · Score: 1

      No it's not impossible, even back in the 80:s it was possible to store files such that only the very last commit could be corrupted in a power outage. Yes HD/SSD:s does not always tell the truth about fsync but it still does not make it impossible to avoid the major data loss that you see with todays systems.

    49. Re:Guy made a mistake by angel'o'sphere · · Score: 1

      Exactly: the very last commit will be currupted in a power outtage.
      Hence you can not continue where you left when you reboot.

      Wow, that was easy again.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    50. Re:Guy made a mistake by F.Ultra · · Score: 1

      No, the very last commit might be currupted. So in 99% (and probably more) of cases you should be able to continue even after a power outage. However losing just the last changes which should, for a word processor, be just a few sentences or characters maximum, is a far cry from todays systems where you loose everything since the last time you pressed save. Now some word processors does an autosave every 5 or 10 minutes but that is way to seldom (and I'm talking about all and every computer program and not just word processors) and it also AFAIK only save the text as it is and not the full undo/redo history among other things.

    51. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      > Every action a user can take should be undo-able.

      Forgiveness is a basic principle of user interface design that goes back at least to the original Mac guidelines.

      "The system should treat all user input as sacred."
      "A computer shall not harm your work or, through inaction, allow your work to come to harm."
      "An interface is humane if it is responsive to human needs and considerate of human frailties."

        – Jef Raskin, The Humane Interface

    52. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      He didn't know how to commit his work. Therefore, Git discarded all the uncommitted changes when instructed to do so.

    53. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      Everything you say is true, but I do wonder if there is a case to be made for an additional special case warning along the lines of 'as no commits have ever been made, so this operation will delete *everything*' given this is an easily detected special case and highly likely to be a mistake.

    54. Re:Guy made a mistake by terjeber · · Score: 1

      A developer who finds the interface of VSCode confusing should stop working with computers and become a bus driver.

      A developer who can't recover from he him self, by being a dumb-ass (we all are some times) should not be allowed within 100 feet of a computer.

    55. Re:Guy made a mistake by terjeber · · Score: 1

      Yes, Microsoft's UI should not have allowed this mistake to happen so easily.

      Perhaps the huge warning dialog with the all-caps "IRREVERSIBLE" should have given him a clue. He's clueless.

    56. Re:Guy made a mistake by terjeber · · Score: 1

      Yes, it is partly Microsoft's fault.

      I am a little unsure as to how this is in any way Microsoft's fault. As others have pointed out, this is a feature of Git, not of VSCode. Also, since Microsoft knows that doing this is quite often something you actually don't want to do, VSCode popped a dialog with a very seriously worded warning to this user. The warning included the word "IRREVERSIBLE" in all-caps, to underscore the point that at this moment the user was doing something that might not be so smart. Short of disabling the feature in VSCode entirely, what should Microsoft do? I know for sure that disabling Git features in VSCode would not go down so well with most developers.

    57. Re:Guy made a mistake by terjeber · · Score: 1

      Every action a user can take should be undo-able

      Well, if it should be, that is not a Microsoft issue since Microsoft are not the authors of Git. It is Git that removes all files. Also, when the tool warns you with ALL CAPS that your action will cause IRREVERSIBLE changes to your computer, you are a MORON if you don't know what you are doing and you pres "OK, just make these IRREVERSIBLE changes to my stuff".

      This user has nobody to blame but him self, and he had behaving like a total moron for at least 90 days.

    58. Re:Guy made a mistake by angel'o'sphere · · Score: 1

      If you have a power outage during a commit, it is always incomplete, aka corrupt.
      Perhpas you should read a book about it?

      is a far cry from todays systems where you loose everything since the last time you pressed save. Get a Mac then?

      Now some word processors does an autosave every 5 or 10 minutes but that is way to seldom (and I'm talking about all and every computer program and not just word processors)
      Why don't you check the menu? Go into settings? Set autosave to 30 seconds? Can't be so hard to get a clue about how software works ...

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    59. Re:Guy made a mistake by terjeber · · Score: 1

      This guy is clearly a moron, but there are a lot of morons out there, and software should be designed with that in mind.

      No. Never. Ever. Not development tools. If you design development tools that assume the user is a complete computer illiterate then the development tool becomes impossible to use for people who actually know how to use computers. Development tools should be developer friendly, not idiot-proof.

      The worst thing about this guy is not that he is a moron, we all are from time to time. I've never lost months of work, but I have lost a week of work at one point in time by not pushing for an entire week. It was idiotic. I was angry. I had to work insanely hard to make it up. What I didn't do, and what I never do as a developer, is blame someone else for my own fuckup. This guy is the worst kind of moron. A moron who won't take responsibility for his own fuckups. Since we all fuck up from time to time, morons like this guy is poison in a development environment.

    60. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      Visual Studio Code is open sourced, so its no MSs fault. https://github.com/Microsoft/vscode

    61. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      The problem here is that the context nor the prompt dialog defined clearly what "ALL" means. eg. Perhaps it means, ALL changes made since when VSCODE was last opened? Naturally I would assume that a smart source control system would automatically save work frequently without having to "manually commit" anything. After all, video games save your game state automatically as you progress, why should I expect anything different here? If this was my context, "ALL" would mean "all since last automatic save", which presumably happens atleast once a day, or every time app succesfully runs.

    62. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      But if no changes were made, you (I) would expect the function do absolutely nothing. It says it will delete changes, not the the source code.

    63. Re:Guy made a mistake by F.Ultra · · Score: 1

      The only mention of a power outage during a commit was this particular reply from you but somehow you think that I should read a book about it? Does this book contain information on how to read post that are not yet posted?

      And btw great work to just ignore the bigger picture, didn't I mention that I talked about all softwares and not just word processors in the very text you quoted? Autosave in a word processor does not save full undo/redo history, autosave in a word processor does not save in commit fashion but in a two step dance (save as tmp, rename to real filename)

    64. Re:Guy made a mistake by angel'o'sphere · · Score: 1

      You or your parent claimed that a computer is able to recover completly if power fails during a transaction.

      Your rename example is a perfect example why it can not work.

      You want to rename "something" into "anything" and after 'any' is written to the disk, the file's name is "anymthing" (and that super simplyfied, because in reality the whole disk block contains unpredictable data and your directory might be destroyed and the original file as well as the new one are both lost)

      Yes, you should read a book about it instead of posting your stupid ideas how computers or physics or any other stuff works.

      The idea of transactions is precisely this: either everything works and even after a power failure you can recover 'behind that transaction' or you can recover 'in front of the transaction'. If the power fails during the transaction, thet it depemds on the system, if it can replay the transaction and 'forward behind it' as if it had succeded. Nevertheless, every thing you are currently doing ... in a transaction that has not enough data written to disk successfully, is always lost completely!!

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    65. Re:Guy made a mistake by F.Ultra · · Score: 1

      No, no one in this thread talked about a power outage during a transaction until you brought it up with your previous post. That a transaction will be lost if it happens during a power outage is a no brainer so I don't even know why you keep arguing this, or you like to kick in open doors?

      Something tells me that you read only parts of other peoples posts before you post yourself, because "my example" with rename was not my solution, it was my description of how i.e word processors does it today and was part of my explanation on why it does not work (remember here that your claim was that how they currently work is just fine and all a user had to do was to change the settings of said application) so why you reply back with "it does not work" when that was exactly my point is just strange.

      Instead of reading your books you should perhaps take some time to read the actual posts that you are replying to, that should lessen your confusion greatly.

    66. Re:Guy made a mistake by angel'o'sphere · · Score: 1

      Sorry, you are mistaken.
      I originally answered to a post where the author said: 'I don't want to save manually, I expect a modern computer to keep every keystroke on disk, so that after a power outage it is exactly at the same point where it happened'
      I was not even the first one using the word transaction, that was a response to my answer were I said: 'this is impossible'.

      Sorry, that I over read your 'it does not work' part :)

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    67. Re:Guy made a mistake by F.Ultra · · Score: 1

      And that author was me, what I did write was:

      There is really no reason why you shouldn't be able to write in a document, experience a power outage, boot the computer, load the document and be able to continue right where you left of, including full undo support back to the first edit to the document.

      I can see why you where initially confused since I kind of worded it badly, but I never meant it to be a power outage at the commit, if it had I would never expected a full recovery :)

    68. Re:Guy made a mistake by angel'o'sphere · · Score: 1

      Oki, doki. My bad then :)

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    69. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      That a transaction will be lost if it happens during a power outage is a no brainer

      Why? To me, the no-brainer is "the computer should preserve the contents of memory on power loss."

      We have backup batteries, UPS's, and flash memory. There's absolutely no reason for a modern computer to EVER lose data due to power loss.

      Hardware failure is a different matter; nothing can safeguard against absolutely every occurrence, but redundancy goes a long way.

    70. Re:Guy made a mistake by F.Ultra · · Score: 1

      I hear you but you basically need something like core memory for that and unfortunately that is way too slow for today's processors. But yes a very small battery backup in the PSU that would allow the system to shut-down orderly on a power outage would go a long way, the problem here is that with current battery technology the lifetime of such a small battery pack is quite limited so it would need to be switched after a few years, of course not that a big deal really.

    71. Re:Guy made a mistake by Anonymous Coward · · Score: 0

      There aren't any technical or cost barriers - my laptop has a "hibernate" feature, and when the battery runs down it automatically copies the contents of memory to the hard drive and shuts down. When I plug it in, it resumes exactly as it was by restoring the state from HD to memory.

      There's no reason this approach can't be deployed today in every desktop and server, it's nothing but institutional inertia on the designers' part.

    72. Re:Guy made a mistake by F.Ultra · · Score: 1

      Yeah, especially on a laptop one would think that this should have been fixed ages ago.

  3. PEBKAC by Anonymous Coward · · Score: 0

    Dude clicked Discard...

  4. It's called backup by Anonymous Coward · · Score: 1

    Couldn't be bothered to backup your data for over 3 months and run some new tool you've never used before?

    Sounds like PEBCAK

  5. I'm confused too by AvitarX · · Score: 2

    Doesn't NTFS allow for file history ?

    I don't understand how anybody could have an important drive without that turned on.

    --
    Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    1. Re:I'm confused too by Anonymous Coward · · Score: 0

      vss can get some files back, maybe all, if it was enabled and a recent snapshot taken -- but it's hardly a proper backup solution.

    2. Re:I'm confused too by Anonymous Coward · · Score: 0

      File history records old versions of existing files. AFAIK, when you delete a file, it can't be recovered using file history.

    3. Re: I'm confused too by Anonymous Coward · · Score: 0

      Just use undelete. Sounds like he figured out what he dis quite quickly so should work

    4. Re:I'm confused too by AvitarX · · Score: 1

      I thought you could pick the old state of folders too.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    5. Re:I'm confused too by AvitarX · · Score: 1

      I consider it with raid a decent solution.

      Call it 1.5 places not two

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    6. Re:I'm confused too by vux984 · · Score: 2, Insightful

      Forget drive history... the hard drive could fail, or get stolen, or get damaged by lightning or coffee, or deleted by malware.

      Where are the backups?

      Revision control is not backups. NFTS file history is NOT proper backups. A copy elsewhere on the same hard drive or same computer or on another computer via a filesystem mount... is NOT proper backups. An external drive you attach once a week and copy files to is not proper backups. They are better than nothing, and each one is still useful... revision control has lots of uses after all, including recovering from certain messes, but it is not by itself proper backups.

      If you can't survive a ransomware infection and a lightning strike all happening simultaneously with the backups *running* -- then you don't have proper backups.

    7. Re:I'm confused too by AvitarX · · Score: 1

      I personally use revision control to fill the gap with the external i remove and store at work.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    8. Re:I'm confused too by Anonymous Coward · · Score: 0

      Like the other guy says, just do the folder. But you can also do the file by creating a new dummy file with the same name as the one you deleted and then looking at the versions of that.

    9. Re:I'm confused too by mwvdlee · · Score: 1

      revision control is not proper backup, but are you aware that all modern revision control systems are atomic? A "backup" is either perfect or non-existant.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    10. Re:I'm confused too by redmasq · · Score: 1

      It may help to specify what constitutes a proper backup.

      In my case, I use an automated weekly full disk image to a larger external drive. In addition, I have configured automatic nightly zip and store on different machine on my network of a few key document directories, 60 day rotation. One folder contains automatic syncing (within a minute or so) to Google drive for stuff in which has a lower privacy threshold. I also have a reminder set on my phone to verify that the backups are actually working every six months or so. Besides that, I also keep a local SVN setup that has its own automatic zip and store of the repo itself weekly.

      In regards to the original post, I think there is blame to share. A good UI should prompt for confirmation when a impossible to undo operation is pending. On the other hand, until something gets into version control, and even after, a mild amount of paranoia is good. I duplicate my working copy and the trunk prior to large merges, for example. Usually, it is a complete waste of time; however, it did on two occasions in the last year saved me from a lot of headache.

    11. Re:I'm confused too by networkBoy · · Score: 1

      define "Survive"...
      In that scenario I would lose 1 week's worth of work at a maximum.
      On critical projects I would lose ~24-48 hours worth of work.

      Of course I find the situation to be highly unlikely... so am willing to accept that risk level.

      --
      whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
    12. Re:I'm confused too by vux984 · · Score: 1

      revision control is not proper backup, but are you aware that all modern revision control systems are atomic? A "backup" is either perfect or non-existant.

      That's really beside the point. Revision control is not a backup because you can easily destroy or damage the entre repo while working against it. A simple git repo locally is literally just a hidden folder in the working directly that the git tools treat special... and that you aren't normally supposed to directly touch. But it's there and its vulnerable to all kinds of stuff. You can delete the folder, or corrupt it, or use git commands wrong to clear it out, if the hard drive fails, it fails. It's vulnerable to all kinds of stuff.

      Offsite revision control with git starts approaching 'backup' levels of robustness. When think just in terms of commits. But you can still remove branches and delete things accidently etc. If you are going to "play" with the git repo management commands ... you really need a backup of the repo itself; or you can do some REAL damage; because not everything can be undone.

    13. Re:I'm confused too by vux984 · · Score: 1

      define "Survive"...

      Be able to restore your data to a point in recent enough time that you deem the loss acceptable.
      With some stuff like code, you can lose a week... with other stuff like photos -- gone forever is gone forevor. you lose the wedding shoot from 3 days ago... and the fact that you still have the ones from the week before isn't going to help that particular couple.

      Of course I find the situation to be highly unlikely... so am willing to accept that risk level.

      Yeah, I used to do a weekly backup to an external USB drive. I had an 'electrical event' while it was plugged in and I was running the backups that fried both the PC's drive, and the external at the same time. (The PC power supply fried out spectacularly and fried the mainboard and pretty much everything it was attached to.

      I *should* have had a 2nd external drive that I swapped back and forth with or something; so that I always had at least one drive not attached. But I didn't. I was actually able to recover the data via one of the clean-room platter transplant services but it cost about $1000... so i was lucky.

      In hindsight I was also vulnerable to fire/theft/flood, and would have been even with additional hard drive.

      So now, I don't consider anything onsite only as being sufficient. I've seen too many people lose everything despite having a backup on there home NAS or something; when both get damaged or stolen at once. And with malware (ransomware) I've seen people lose their backups because the malware was able to 'reach' the backup drives via file system mounts, even on remotes. So I don't consider that sufficient.

      Some sort of cloud based system that uses a backup agent (so you aren't mounting the remote file system) like carbonite or crashplan etc... plus periodically connected local drive or 2 ... that's about the minimum that I consider adequate these days.

      Unlikely stuff happens. I'm not trying to make backups to survive world war 3 or a comet strike. But malware infections and electrical shorts happen, and its not difficult or expensive to safeguard against them.

    14. Re:I'm confused too by networkBoy · · Score: 1

      I have a 36 hour cron job rsync that runs on my critical work.
      Everything else is weekly.
      Plus a pair of local drives that take turns being on the system every other week.

      --
      whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
    15. Re:I'm confused too by Anonymous Coward · · Score: 0

      For anyone who's guessing at what might actually constitute proper backups, it's not enough to be told what not to do.
      For the curious: offsite, encrypted multiple immutable (or offline) historical authenticatable copies at multiple secure geographic locations. Two locations is pushing it, three or more is preferable.
      - Offsite in multiple locations so a natural disaster, fire, flood, theft, vandalism etc. at one location won't take you out.
      - Encrypted to protect against sniffing in transit, or against theft; whether by employee or by a 3rd party hosting service or by thieves. (Petty thieves WILL steal unfenceable shit that has absolutely zero value to them for any or no reason.) There are degrees of encryption effectiveness, like having a different key for every backup vs. not, but any encryption is better than none.
      - Offline or otherwise effectively immutable copies in place so a rogue script, virus, disgruntled employee, or dedicated hacker won't be able to wipe or tamper with all your backups remotely. Physically secure and remote password secure.
      - Historical copies that go back a reasonable distance in time in case
      - Authenticatable means you can confirm that a backup copy has not been tampered with or if it has suffered from bit rot.

      For bonus points:
      - Additional parity data (e.g. using par2) is good so that you can recover from small media failures or bit rot. Useful since a single bit failure in encrypted data can make a whole block undecryptable.
      - You can record and stream out database replay logs and back those up daily too. This'll let you recover up until the point you fat-fingered it.

    16. Re:I'm confused too by Thumper_SVX · · Score: 1

      It does, and I honestly wish that it was enabled by default in consumer versions of Windows. As it stands, I set up all my Windows machines to have file history stored on a remote disk on my file server, so if I lose something it's usually only a few clicks away (unless my laptop is outside the house, then I have to wait until I get home to do the restore)

      Disk space is a lot cheaper than re-building your work!

  6. Compatibility Mode by T.E.D. · · Score: 0

    Sounds like it was is SourceSafe compatibility mode.

    1. Re:Compatibility Mode by Anonymous Coward · · Score: 1

      "Discard" is a Git term and does what it says. He would have had the same problem with SourceTree, WinGit, Git CLI or any other Git-enabled tool.

  7. Git by irrational_design · · Score: 4, Informative

    Fortunately he can just retrieve his files from his Git repository, right? Or... he just learned a painful lesson of why you always use a code repository.

    1. Re:Git by Hardhead_7 · · Score: 2

      I think it's insane to do three months of work without a backup. I get worried if I don't push my commits once a day.

      On the other hand, I definitely agree with him that VSCode shouldn't delete files when it doesn't detect a git repo. And it should be clearer about what it's doing.

    2. Re:Git by Pascoea · · Score: 1

      Side comment/anecdote... I had to reformat/reinstall my home multi use gaming/programming/ general use windows PC, I have a main SSD that holds the OS and most programs and a separate "data" raid array to hold the "important" stuff. (And a remote git repository with nightly commits, and a recent pull onto a different machine, and a backup of the data drive) Figured I was safe, so I just formatted and reinstalled. No problem until I realized that XAMPP was running on the SSD. Database fucking gone, no backup, no secondary copy. Luckily I had an SQL dump from a month or so prior, but still took me 2 nights work to get it back to where I could continue developing, and a bunch of regression testing to figure out what else was screwed up. Moral of the story...I now include a full SQL dump in my nightly commits.

      Second thought, what is the PROPER way to make sure your database structure and supporting data are included in your code commits? For example, structure only isn't enough because all of the RBAC info is stored in the database.

    3. Re:Git by phantomfive · · Score: 1

      Real men put their code on FTP and let the world back it up

      --
      "First they came for the slanderers and i said nothing."
    4. Re:Git by PmanAce · · Score: 1

      He didn't have a repository, his fault.

      --
      Tired of my customary (Score:1)
    5. Re:Git by swillden · · Score: 5, Interesting

      Fortunately he can just retrieve his files from his Git repository, right? Or... he just learned a painful lesson of why you always use a code repository.

      I have to take this opportunity to tell my favorite oh-shit story.

      Some twenty-odd years ago, I was working on an embedded system project which had about 60 person-years of development effort into it (20 developers, three years). We worked on HPUX workstations with our home directories NFS-mounted on a big Network Appliances NFS server. The server was pretty cool tech for the day, making use of RAID for redundancy, with nifty snapshotting features, including automatic snapshotting that created a set of hidden subdirectories in each directory with your files as they were an hour before, two hours before, etc. Getting back any old version was super easy. Plus we all used CVS, and the CVS server also used NFS storage.

      So... all of our eggs were in one basket, but it was a highly-reliable and flexible basket and, of course, the sysadmin made nightly backups, rotated the tapes offsite, etc. The backups even included the snapshots, providing quite fine-grained history from any point in time. So not bad.

      Well, one day something went wrong, and the NFS server lost everything. I don't know if it was hardware failure, if the sysadmin accidentally did something like "rm -rf /", or what. But it was all gone. All of the developers' home directories, with their working copies, and the central CVS repository. Every Single Line Of Code, all of the design documents other that what happened to be laying around in hardcopy, everything. 60 person-years.

      Oh shit.

      But, backups, right? No.

      Not one.

      The sysadmin had never tested his backups, and it turned out that his backup script didn't have permission to read any of the directories where the important data lived. The backup tapes were all useless. He had dozens of methodically-archived off-site copies of the NFS server system binaries. You know, the ones that come on the installation media.

      OH SHIT!

      Luckily, we had one major customer that was so big, financially, and so influential in the relevant industry, that when they signed their contract to buy our product, they made us commit to keeping a developer on-site, full-time. So we all took turns spending a couple of weeks at a time living in a hotel and working in their facility, on the other side of the continent. And, most importantly, there was a development workstation there. With a local copy of the code that was updated via FTP as needed.

      Now, for you young'uns that only know about distributed version control systems, CVS wasn't (isn't) such a beast. In CVS there's one central repository which has all of the versioned history, all of the branches (not that there were many, because working with branches was a pain in the ass), all of the tags, etc. When you check out the code, you get only the current head revision of the one branch, no history at all.

      That's what this one remote workstation had. A checkout of HEAD, as it was a couple of weeks before the disaster. We carefully copied that, and FTP'd it back home, and used it to start a new, fresh, CVS repository. All of the commit history was gone, and a couple of weeks of work by 20 or so people, but we had nearly-current code. All of the design docs and other bits and pieces were gone, but we had code.

      You may be wondering if, at this point, the sysadmin got canned. He did not. He was called onto the carpet and told that we HAD to have good, tested backups going forward. He agreed that it would be his top priority. A couple of weeks later, he reported back to senior management that we had good backups.

      My boss decided to test it. He disabled snapshotting of his home directory, created a file, put some stuff into it, waited a day (so it would get backed up to tape), then deleted it and walked over to ask the sysadmin to recover it for him.

      The backups still didn

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    6. Re:Git by Anonymous Coward · · Score: 0

      You just can't help stupid.

    7. Re:Git by Anonymous Coward · · Score: 0

      From reading the article, I think he did use git, except that he hadn't checked anything back in for three months, and the IDE chose to trust the git repo over his local files.

    8. Re:Git by tibit · · Score: 1

      Use CI for development. Then you always start from a clean slate and it's procedurally required that you have all the data needed to get a full build environment going from scratch.

      --
      A successful API design takes a mixture of software design and pedagogy.
    9. Re:Git by pjbgravely · · Score: 1

      Great story. I love your sig, but did you know that cowards can't see sigs?

      --
      Star Trek, there maybe hope.
    10. Re:Git by Anonymous Coward · · Score: 0

      Git may be the problem. He is committing his work to git, and thinking it is going to some sever somewhere. If all you have used is SourceSafe, or svn, you will have some built in assumptions that don't apply to modern DVCS, and that can come back and bite you in the ass in situations like this, especially if you are coming from SourceSafe where you are limited to a single working copy, so get used to deleting your workspace so you can check it out somewhere else.

    11. Re:Git by TheRaven64 · · Score: 1
      It did detect a git repository, but one with no files. He then told it to discard all changes since the last commit, which (because there were no commits) meant discard all files. It then popped up a big warning saying that it was going to delete files and that this action is irreversible. He then told it to proceed. It then deleted all of his files.

      A better UI might have been to move all of the files to the recycle bin, but that doesn't work well with modified files. Perhaps creating a diff and dumping that in the recycle bin would allow undo a bit better, but there's a warning that the operation can't be undone (which, by the way, isn't there with the command-line git tool).

      --
      I am TheRaven on Soylent News
    12. Re:Git by shutdown+-p+now · · Score: 1

      He was using a source code repository. Git specifically, in fact.

      The problem is that he had three months of uncommitted changes in that local repo of his. Not just uncommitted - unstaged.

      So then he opened the Git panel in VSCode. And it told him - hey, dude, you've got like 5000 changed files here. He didn't like it, so he dug around, and found "Discard all changes" command (it's not even prominently displayed, you need to bring up the context menu for that). For some reason, he decided that it's the magic thing that's going to make things better. He clicked it, at which point it popped up a warning dialog with this text:

      "Are you sure you want to discard ALL changes? This is IRREVERSIBLE!"

      And he clicked on the button in that dialog that said "Discard ALL Changes".

      At which point it basically did git clean -f -q; git checkout -- ..

      So this is a case of taking a shotgun, loading a shell into it, taking the safety off, aiming it at your foot, and pulling the trigger - because you have no clue about how guns work or what they do, but you've heard that having one is essential, so you got it, and then decided to do something with it without bothering to learn anything at all.

    13. Re:Git by Anonymous Coward · · Score: 0

      the only thing i cant stand more at work than incompetence is a fucking liar. i used to work with this guy who could never admit a mistake and used to do some things that were wildly above his skill-level.

      One sunday a customer of ours had their SAN shit itself. I am the one tasked with finding what exactly went on once we work with the vendor to get it back online.

      I had this lying fuck in our audit logs establishing a VPN to our office from home mid-morning on Sunday, logging in via RDP to his workstation.

      From the customers audit logs I see a VPN connection from our office, then logins to the SAN from the IP address assigned to the VPN connection from our office. SAN logs show he for some reason INITIATED A FIRMWARE UPGRADE OF ALL HDD's, which failed spectacularly.

      In the course of discovering this I go to him with what I've found. He flat out lies to my face until the point I am suggesting we need to call the police because we are now investigating a compromise. Only at this point does he weaken and say that maybe he accidentally clicked something when he was doing some helpdesk work. Righto.

      So I document all this, hand it to management as requested... and nothing happened. This is a helpdesk guy who was fucking around with customers business critical SAN's when he had no business even connecting to their networks, wasted a couple of days of my time to trace and document what happened and told numerous lies before it was clear he had to stop with the bullshit. I couldn't believe it. He got a really soft warning not to do that kind of thing again.

      I had another job within 2 months and got my name the fuck away from that company.

  8. Nothing is ever deleted by Anonymous Coward · · Score: 0

    Go grab Recuva or something and get the data back. This seems more like a PEKAC error than anything else.

  9. So, let me get this straight... by djbckr · · Score: 5, Insightful

    He clicks "discard" and it deletes the files. This seems a reasonable outcome. Did he not have any backups? I'm pretty sure that is the *real* WTF.

    1. Re:So, let me get this straight... by Anonymous Coward · · Score: 0

      He clicks "discard" and it deletes the files. This seems a reasonable outcome. Did he not have any backups? I'm pretty sure that is the *real* WTF.

      Just another member of the M$ nanny league of developers. You know the type, never worked with anything other than a graphical ide .. never heard of cmdline, vi or emacs.

    2. Re:So, let me get this straight... by kurkosdr · · Score: 1, Redundant

      Why did they name it "discard" instead of "delete". Usually "discard" means drop pending changes or discard a message on screen.

    3. Re:So, let me get this straight... by evilj614 · · Score: 0

      Reminds me of the guy years ago that sued Winnebago when he set the "cruise control" on his new RV and it wrecked after he got up to go fix himself a sandwich in the back. Unfortunately, that guy won his lawsuit because the user manual didn't say not to do it. So maybe this dude should sue Microsoft for not including a warning in the user manual? Regardless, I bet: 1) he's a millennial 2) it's your fault... not his. I can't comprehend how you go three months working on something and not do a single commit to a repo somewhere, not back the code up, or start pushing buttons you don't know what they do.

    4. Re:So, let me get this straight... by Anonymous Coward · · Score: 0

      I just quickly went into three graphical source control IDEs that integrate with git. Two of the three used discard to discard your working copy changes. The one that didn't, sadly, is Visual Studio (proper, not Code).

      I can't remember which tool, but there was one I used not too long ago that isn't readily available to me where I remember not being able to figure out how to discard my working copy changes (hey, look, the word discard is in there too) because it wasn't called discard.

    5. Re:So, let me get this straight... by digital_fiz · · Score: 2, Informative

      It does mean discard pending changes which in his case happened to be everything or mostly everything? Both Git and VSCode are functioning properly he just clicked buttons without understanding what they did first. if he had copy/pasted a git checkout or git rebase code snippet he got on some website that wiped his stuff out and he was surprised this would have a different reaction but its no different. 2 major issues I see: - Not having backups of an obviously huge project either in git already or in a different location? - Why was he testing out an editor and clicking buttons he had no idea what they did on such a important project?

    6. Re:So, let me get this straight... by Anonymous Coward · · Score: 0

      Yep pretty much. IF he is not using an SSD he may be able to get them back IF he does not do anything else. There are several utils out there free and paid that can help recover the files. If it is an SSD he is SOL.

      Version control and backups. This guy just learned the same lesson we all learn at some point. Even Jesus saves.

    7. Re:So, let me get this straight... by The+MAZZTer · · Score: 1

      The problem is his files were unversioned and he did not expect the rollback to affect unversioned files, which it did.

    8. Re:So, let me get this straight... by Anonymous Coward · · Score: 0
      *sigh*

      Reminds me of the guy years ago that sued Winnebago when he set the "cruise control" on his new RV and it wrecked after he got up to go fix himself a sandwich in the back. Unfortunately, that guy won his lawsuit because the user manual didn't say not to do it.

      You realize that didn't actually happen.

      Are we, as a society, getting more stupid?

    9. Re:So, let me get this straight... by Nethemas+the+Great · · Score: 1

      Pretty sure he did discard pending changes... Leaving yourself hanging in the wind for 3 months is the real problem. Yes he's steaming, yes he clicked on something that may (or not) be readily misinterpreted. But there's no one to blame for 3 months of potential loss made real but himself. Would he go on a tirade about how the HDD manufacturer should have made provisions for when his drive crashed? You always protect your deltas with the shortest reasonable interval. Stuff happens.

      --
      Two of my imaginary friends reproduced once ... with negative results.
    10. Re:So, let me get this straight... by F.Ultra · · Score: 1

      Except of course that the Winnebago story is just an urban legend. http://www.heraldtribune.com/n...

    11. Re:So, let me get this straight... by Anonymous Coward · · Score: 0

      Sounds like vs code just did the world a favour by deleting his code before it could be spread any further...

    12. Re:So, let me get this straight... by Anonymous Coward · · Score: 0

      He probably had RAID - you don't need backups with RAID!
      trollololool

    13. Re:So, let me get this straight... by gnasher719 · · Score: 1

      Perforce has a command "obliterate". _That_ command will totally obliterate a file. Remove all copies from version control as if it never existed. Used for passwords accidentially checked in, or for gigabyte uncompressed marketing videos.

    14. Re:So, let me get this straight... by thegarbz · · Score: 1

      This was the initial commit. ALL his code was a big pending change.

    15. Re:So, let me get this straight... by Anonymous Coward · · Score: 0

      because it does discard pending changes, but if you are a retard and never commit any changes then those pending changes are everything.

    16. Re:So, let me get this straight... by shutdown+-p+now · · Score: 1

      That's exactly what it did. He had 3 months worth of uncommitted, unstaged changes in his local Git repo. And he asked VSCode to discard those changes.

      It even pops up a warning dialog telling you that it's an irreversible operation (in screaming caps even!), and asking whether you're sure you really want to do that.

  10. Not a typo by Anonymous Coward · · Score: 0
  11. undelete by Anonymous Coward · · Score: 0

    try some undelete programs

    1. Re:Undelete by Anonymous Coward · · Score: 0

      Windows OS swap and other garbage being stored by internet browsers would overwrite his files, depending on the size of his HD or SSD drive he might be successful recovering some files.

    2. Re:Undelete by Anonymous Coward · · Score: 0

      Hoping he doesn't recover 5000 files named on a variation of "????????.???" with all the hierarchy lost and flattened.

  12. Oh my god will you bloody editors do some work by wonkey_monkey · · Score: 4, Funny

    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.
    1. Re:Oh my god will you bloody editors do some work by Anonymous Coward · · Score: 0

      And what the hell is a "three-month"? If that was ever a thing, it hasn't been for about 300 years.

      It's called a "quarter."

    2. Re:Oh my god will you bloody editors do some work by Anonymous Coward · · Score: 0

      >I think someone accidentally a word.

      That's the joke. Y'know, new age stuff. ...

      Time to go back to the retirement home grandpa.

    3. Re:Oh my god will you bloody editors do some work by Anonymous Coward · · Score: 0

      Woooooooooooooooooooooooooshhhhh....

      I think somebody doesn't the joke.

    4. Re:Oh my god will you bloody editors do some work by TheRealMindChild · · Score: 1

      thatsthejoke.jpg

      --

      "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    5. Re:Oh my god will you bloody editors do some work by Anonymous Coward · · Score: 0

      And what the hell is a "three-month"?

      In developer terms, about five hours of work.

    6. Re:Oh my god will you bloody editors do some work by kurkosdr · · Score: 2

      A work that took three-months to complete. It is a measure of effort.

    7. Re:Oh my god will you bloody editors do some work by Anonymous Coward · · Score: 0

      Well, yea, it's just usually called a quarter ...

    8. Re:Oh my god will you bloody editors do some work by 93+Escort+Wagon · · Score: 1

      And what the hell is a "three-month"?

      Maybe it's like a three-way?

      --
      #DeleteChrome
    9. Re:Oh my god will you bloody editors do some work by null+etc. · · Score: 1

      I think someone accidentally a word.

      A developer accidentally three-month of his work
      Was thrown out by his boss, a big jerk
      Lost some group emails too
      Trump screamed "What'd Hillary do?"
      And now outside the White House he doth lurk

    10. Re:Oh my god will you bloody editors do some work by Pfhorrest · · Score: 1
      --
      -Forrest Cameranesi, Geek of all Trades
      "I am Sam. Sam I am. I do not like trolls, flames, or spam."
    11. Re:Oh my god will you bloody editors do some work by Anonymous Coward · · Score: 0

      A work that took three-months to complete. It is a measure of effort.

      A whoosh that took three-months to complete. It is a measure of missing it.

      sorry. i'll go back to work now.

    12. Re:Oh my god will you bloody editors do some work by Anonymous Coward · · Score: 0

      How many three-months?

    13. Re:Oh my god will you bloody editors do some work by wonkey_monkey · · Score: 1

      Memes don't belong on any site that wants itself to be taken remotely seriously as a source of news, especially when they are indistinguishable from typos.

      What next, stories about how Facebook "can haz all our datas"?

      --
      systemd is Roko's Basilisk.
    14. Re:Oh my god will you bloody editors do some work by wonkey_monkey · · Score: 1

      Memes like that don't belong on any site that wants itself to be taken remotely seriously as a source of news, especially when they are indistinguishable from typos.

      What next, stories about how Facebook "can haz all our datas"?

      --
      systemd is Roko's Basilisk.
    15. Re:Oh my god will you bloody editors do some work by Anonymous Coward · · Score: 0

      >I think someone accidentally a word.

      That's joke. Y'know, stuff. ...

      Time to back to grandpa.

    16. Re:Oh my god will you bloody editors do some work by TheRaven64 · · Score: 1

      Three months is a noun phrase, three-months is an adjective phrase. Three-month is a nonsense.

      --
      I am TheRaven on Soylent News
    17. Re:Oh my god will you bloody editors do some work by Anonymous Coward · · Score: 0

      Read the first line of the summary again. It's missing the verbum - as to be seen in GP's quote.

      It's interesting, how our brain keeps autocorrecting the things we see.

    18. Re:Oh my god will you bloody editors do some work by michael_wojcik · · Score: 1

      In American English, "three-month" would be the more common form of the adjectival phrase:

      I engaged in a three-month English-usage flame war on /., to no avail.

      The plural variant is, IME, common in British English, and may indeed be dominant there.

      A quick Google Ngram Viewer check suggests the plural form was more common historically, but was displaced by the singular one around 1935, and the latter is now far more popular.

  13. Backups? by Anonymous Coward · · Score: 0

    News at nine! Always never backup your hard earned work before installing a never before used program that is going to "manage" your files for you.

  14. This guy is a moron by Anonymous Coward · · Score: 2, Insightful

    What would he have done if his hard drive crashed in that three month span? Who doesn't back up their work daily to something...anything?

    This article should be "Moron developer blames software for his stupidity".

    1. Re: This guy is a moron by Anonymous Coward · · Score: 0

      Here's his response to people wondering why he didn't have a backup:

      "@remcoros yeah, so the damage done by the destructive bug in the code is now my fault for not being a clairvoyant and seeing this piece of shit software was going to fuck up my files. I don't need to explain why I don't have a private repo with my stuff. It is the software's concern NOT to destroy the integrity of a computer like a damn virus. You come here, see my despair and berate me for something that was not my fault, and has happened to a lot of other people? Fuck you."

      It's not his fault! LOL

    2. Re: This guy is a moron by amxcoder · · Score: 2

      This is the same method that a lot of people use to come to the conclusion that having backups is important. Usually after the first or second time a person looses important stuff, they realize that being proactive and having some kind of backup plan (any backup plan) is better than none. Maybe his backup choices will be clearer to him now.

      Its amazing how many people say "I don't have anything that's important enough if I loose it...." until they actually loose it, then they are devastated. It's also amazing how many people *think* they'll be ok, because they have the important files duplicated somewhere, until they need to find that duplicate, and are looking on all their various computers/laptops, flash-drives, online file storage, and mobile devices, and the best they can find is a copy that's like a year out of date if they are lucky...

      I believe the old saying "once bitten, twice shy" applies to backups here... Maybe he will wisen up and not rely on a single copy of his files if they are so important.

    3. Re: This guy is a moron by Anonymous Coward · · Score: 0

      If he'd loosed it maybe it would've come back to him.

    4. Re: This guy is a moron by Anonymous Coward · · Score: 0

      So much letting loose. Zipper up, people!

    5. Re: This guy is a moron by sheph · · Score: 1

      Well that's nice. Get pissed all you want. But your stuff is still gone. And if you'd taken a backup it wouldn't be. Now here's your opportunity to learn for the future. Alternatively you can cuss and scream and find yourself in the same position next time.

      --
      I don't believe in karma, I just call it like I see it.
    6. Re: This guy is a moron by freeze128 · · Score: 1

      I believe the old saying "once bitten, twice shy" applies to backups here.

      In the late 80's, Great White was literally singing the virtues of backing up your data.

  15. 3 months... by Anonymous Coward · · Score: 0

    ... with no backups or version control? The files were doomed to be lost one way or another

  16. Then he restored from backup and calmed down again by Anonymous Coward · · Score: 1

    Right?

  17. What? No backups? by Anonymous Coward · · Score: 0

    I can see how you can accidentally delete stuff... But no backups?

    We keep 3 months worth of backups. Just sayin'....

  18. Mh by Anonymous Coward · · Score: 1

    Five thousand files an no backups?
    Five thousand files and no good version control systems?
    Five thousand files and no snapshots?

    May I ask if your machine physically crash, get stolen etc?

    I know that Windows guys are... Well... Brave... But...

    1. Re:Mh by Anonymous Coward · · Score: 0

      May I ask if your machine physically crash, get stolen etc?

      It doesn't even need to be anything that drastic, what if something you tried to implement didn't work and you just wanted to get back to a clean version from before you made that change? Or maybe something you did yesterday broke a feature from last month and you don't find out until next week? I'm not a developer, but I know better than to have nothing but a working copy of anything.

  19. Alternative to ... no version control? by Anonymous Coward · · Score: 0

    So basically ran git reset --hard ^HEAD without backing up his folder first... are we sure they are a developer? From his own mouth: "It said: are sure to discard all the changes?"

  20. Always backup by Anonymous Coward · · Score: 0

    3 months and the code was not backed up somewhere?

    I only trust version control to a certain point. I think TFS and Git are great compared to horrible version control software I used in the past; however, I still back up my stuff time to time. Especially after 3 months... WTF?

  21. no backup? by Anonymous Coward · · Score: 0

    The guy doesn't make backups at all? What if the cat jerks the power cord and his laptop falls off the desk? What if his laptop is stolen out of his hotel room? What if his hard drive just up and decides that today is the day it's going to die?

  22. Backup, Backup, Backup... by Anonymous Coward · · Score: 0

    All IT should worship at the altar of Backups. Loosing a days work I can see, Loosing a weeks work less so. Loosing several months worth? The blame is firmly on the developer. In the meantime, if you are using windows turn on snapshots to give you some recovery, but still Backup, Backup, Backup. Make it part of your end of day or beginning of day routine and LIVE IT.

  23. News at 11 by Anonymous Coward · · Score: 0

    and his dog ran away

  24. Blaming the victim = bad by Anonymous Coward · · Score: 5, Insightful

    The software redefined the semantics of "discard" without informing the user. In Git, discard means "drop pending changes". In VS Code, apparently, discard means "delete and purge all historical references --force". How the hell can the VS Code devs justify introducing such a dangerous and confusing change?

    Captcha: horror

    1. Re: Blaming the victim = bad by Anonymous Coward · · Score: 0

      That is a disaster, however, it would only be his most recent copy. The fact that it was his only copy is so mindboggingly stupid that it becomes the story.

    2. Re:Blaming the victim = bad by Anonymous Coward · · Score: 0

      There's no victim here, except of bad practices and willful ignorance. This is like someone used to taking a taxi (or self driving car), getting into car and crashing when they neglect to push the brake. "Stupid damn car didn't stop by itself...!?"

      Learn how to use tools... And use revision control with backups. Duh...

    3. Re:Blaming the victim = bad by Anubis+IV · · Score: 1

      The software redefined the semantics of "discard" without informing the user.

      What happened to him is certainly not a good situation, but I don't see how VSCode is redefining anything here.

      You reference Git, but Git's discard action is presented as discarding changes, whereas he describes being presented with a prompt to discard his files and didn't pay enough attention to realize the difference. While I'm sympathetic to his situation, "discard" is defined as "To throw away; reject", which is exactly what happens both in Git and VSCode. It's just a matter of what's being discarded.

      In the end, the problem here is entirely of the PEBKAC variety. Moreover, as developers we have access to powerful and destructive tools. If you don't know your tools well enough to use them safely, don't use them with anything that you'd be upset if you lost. A developer who doesn't know that and doesn't take proper precautions is a developer who's getting closer one day at a time to when they'll learn that lesson the hard way.

    4. Re:Blaming the victim = bad by arth1 · · Score: 2

      It's up to the user to learn how to use the tools. Read the manuals, and understand what things do before attempting them.
      You don't experiment on your only copy of something.

      It's good that this guy is on Windows, though. Imagine the horror of him being on Linux, where almost every command does what you tell it without confirmation. (Which is a good thing.)

    5. Re:Blaming the victim = bad by John+Allsup · · Score: 1

      This is not blaming the victim. Having a solid backup regime _before_ you start any serious work is as important and necessary as putting on safety belts when driving. If a driver doesn't bother to belt up, and goes flying through the windscreen, and then blames the brakes for the injury, pointing out that he should have belted up is not 'blaming the victim'.

      If you are using a piece of software with which you are unfamiliar, you should _always_ take precautions. Think 'computational condom': presume that each piece of software is riddled with bugs until you have checked everything out.

      --
      John_Chalisque
    6. Re:Blaming the victim = bad by Anonymous Coward · · Score: 0

      So, he's been sitting on his pending changes for 3 months? And he's blaming others but himself?

      If I'm not in a state where I can commit changes after *one* working day, I tell TFS to do a shelfset (not sure if Git has an equivalent). No way I'm gonna go longer without an extra copy existing *somewhere* else.

    7. Re:Blaming the victim = bad by jtara · · Score: 4, Informative

      In Git, discard means "drop pending changes".M

      It was ALL PENDING CHANGES.

      He never did any commits!

    8. Re:Blaming the victim = bad by Darinbob · · Score: 1

      Two words that Microsoft promotes often: User Experience. So I believe this VS user managed to get the full experience.

    9. Re:Blaming the victim = bad by bondsbw · · Score: 1

      In VS Code, apparently, discard means "delete and purge all historical references --force"

      Not according to the source.

      It first displays the warning:

      This will DELETE {0} untracked files!

      When the user agrees, it performs git clean -f -q to discard untracked files. No committed history is lost.

      --
      All my liberal friends think I'm a conservative, all my conservative friends think I'm a liberal.
    10. Re:Blaming the victim = bad by Anonymous Coward · · Score: 1

      The software redefined the semantics of "discard" without informing the user. In Git, discard means "drop pending changes". In VS Code, apparently, discard means "delete and purge all historical references --force". How the hell can the VS Code devs justify introducing such a dangerous and confusing change?

      Captcha: horror

      It was and is drop pending changes. He initialized a git repo inside his folder with all his work, then dropped pending changes without commiting anything.

    11. Re:Blaming the victim = bad by gweihir · · Score: 1

      It is not victim-blaming when he did it to himself. Backups are an absolute minimal requirement for any type of professional computer work. So is version-control with an offsite repository and backup of its own for any kind of non-trivial software development.

      These minimal standards are there for a reason. Those not following them have no business complaining when the expected catastrophe hits them.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    12. Re:Blaming the victim = bad by gweihir · · Score: 1

      Seems so. Means he was clueless how his tool works and had no backups. He really has nobody to blame but himself. This kind of amateur-work seems to be becoming more common though, whith "developers" that are utterly clueless.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    13. Re:Blaming the victim = bad by modmans2ndcoming · · Score: 1

      he isn't a victim anymore than I am a victim if I chose to throw out my manuscript.

    14. Re:Blaming the victim = bad by Bert64 · · Score: 1

      Discard means "throw away", a function called discard is obviously going to destroy data and if he wasn't sure *what* data it was going to destroy he should have verified first.

      That, and he should have been keeping backups of anything remotely important. Aside from screwups like this, hardware failure could strike at any moment.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    15. Re:Blaming the victim = bad by Anonymous Coward · · Score: 0

      Re:Blaming the victim = bad

      Not always. Playing in traffic comes to mind.

      In this case I'm willing to say the guy can't be blamed for misunderstanding the interface, but he CAN be blamed for not being prepared for loss events.

    16. Re:Blaming the victim = bad by Anonymous Coward · · Score: 0

      It didn't redefine anything. In 3 months he didn't make a single commit so everything "discard" set it back to a clean state with an empty repo.

    17. Re:Blaming the victim = bad by Anonymous Coward · · Score: 0

      VS Code uses Git, discard means EXACTLY what you said, this numbnuts never committed any changes so ALL his work was a pending change, hence when you tell Git to discard changes it does exactly that.

    18. Re:Blaming the victim = bad by rpstrong · · Score: 1

      You reference Git, but Git's discard action is presented as discarding changes, whereas he describes being presented with a prompt to discard his files and didn't pay enough attention to realize the difference.

      In his words, the prompt did say: "discard all the changes", not "discard all the files".

    19. Re:Blaming the victim = bad by shutdown+-p+now · · Score: 1

      The thing that you missed in this story is that those changes were not commits. They were unstaged files in his local repo, and the command in question is only displayed in the window that shows you the list of such. I'm not aware of any meaning of "discard" wrt Git (or any other source control system really) that, in the context of local files with uncommitted changes, means anything other than what he got.

      And there was no --force there, either - when you do this operation, VSCode asks first. In rather forcible language, even:

      Are you sure you want to discard ALL changes? This is IRREVERSIBLE!

      [Discard ALL Changes] [Cancel]

    20. Re:Blaming the victim = bad by Anonymous Coward · · Score: 0

      Means he was clueless how his tool works and had no backups.

      Probably true.

      He really has nobody to blame but himself.

      Wrong. The tool - the message it conveyed - was (is, still?) very badly designed and worded, and should be assigned part of the blame as well.

      This kind of amateur-work seems to be becoming more common though, whith "developers" that are utterly clueless.

      Assuming the affected person learns from this experience, said person will have become slightly less clueless. With time, the person may end up very clued in.

      You, however, gweihir, will always remain an arrogant ass.

  25. I'm glad SlashDot is loosening up on the lingo by Sla$hPot · · Score: 0

    Otherwise how the FUCK!!! (Yay) could this contribution end up here? Thanks :-)

  26. If he's very very smart by Anubis350 · · Score: 5, Insightful

    If he's very very smart he shut down the machine immediately, mounted the drive read only and recovered the files. The chances are most of them were just unlinked and can be recovered since they havent been overwritten yet

    --
    "goodbye and hello, as always" ~Prince Corwin, from Zelazny's Amber series
    1. Re:If he's very very smart by JimToo · · Score: 1

      Good chance that having had the skillz not to back up for three months he'll have rolled out the old defrag option first so that recovery is as smooth as silk.

    2. Re:If he's very very smart by Anonymous Coward · · Score: 1

      I doubt that somebody that looks for lost files at the Recycle Bin would know how to do that...

    3. Re:If he's very very smart by Bert64 · · Score: 1

      Or an SSD with trim support, so the unused blocks get cleared rather than simply being marked unused.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    4. Re:If he's very very smart by Anonymous Coward · · Score: 0

      I'm pretty sure he's not very smart considering 1. he did three months of work without backup or version control and 2. he they proceeded to test a new VCS with his unbacked up months of work... He probably doesn't have any experience recovering data of a HDD or SSD if he's this idiotic about backups.

    5. Re:If he's very very smart by Matheus · · Score: 2

      If he was very smart he wouldn't be in this situation and whining to /. about it...

    6. Re:If he's very very smart by Anonymous Coward · · Score: 0

      You're asking if a guy who doesn't know how to use version control and doesn't know a single thing about backup protocol is "very smart" ...

    7. Re:If he's very very smart by Ozeroc · · Score: 1

      +1 Funny

      That got a chuckle out of me. Thanks.

      --
      ...
    8. Re:If he's very very smart by aktw · · Score: 1

      Sort of... 1. Anyone could potentially delete the entire code branch on accident when dealing with unfamiliar software. That particular complain is legitimate and seems to be a UI failure. 2. His actual problem is not having *any* backups in place (not to mention deciding to use some unfamiliar software on his only code base). That's a powerful lesson to learn, and one he's probably better off learning now than later in his career. 3. He's not whining to /. about it. He posted his complaint somewhere else and another person linked it here. That said, his general attitude of not taking any responsibility over this is a definite warning sign for any potential employer (way more so than the freak accident).

    9. Re:If he's very very smart by Anonymous Coward · · Score: 0

      Unless a trim is triggered manually by the user, Windows (and any other operating system which supports SSDs and trim) will only schedule an actual trim when it's suitable. I've been able to recover data from an SSD before, but only because it's when I've realized what I've done, launched my data recovery tool and issued a recovery very soon after the deletion. Let the machine idle for long enough and you'd probably have no chance.

    10. Re: If he's very very smart by Anonymous Coward · · Score: 0

      Very very smart = not dumb. Any hacker with an ounce of curiosity should have learned this much about file systems.

    11. Re:If he's very very smart by gravewax · · Score: 1

      If he's very very smart

      He did 3 months of work without a backup or code repository, then tested software he didn't understand on that code AND ignored warnings he didn't understand. He then screamed at people saying he shouldn't have needed a backup. Smart is not a word you could associate with this guy.

  27. The RWTF is looking at the Recycle Bin by Anonymous Coward · · Score: 0

    This guy calls himself a "developer"... and expects that files deleted in an source control tool go to the Recycle Bin? If his work was so valuable, what was he doing without a local backup? And, why go around testing a new (and unknown) tool with the only copy of a several months project? It's sad, but maybe this guy got what he was looking for...

    1. Re:The RWTF is looking at the Recycle Bin by Anonymous Coward · · Score: 0

      You just can't help stupid and stupid is what it is -- stupid.

  28. The lessons of BACKUP !! by ripvlan · · Score: 5, Insightful

    Now that he's 18 - he has discovered the world isn't fair.

    He goes three months and doesn't have a backup? Even in a ZIP file or on a USB drive, or "insert cloud drive service here"

    An unfortunate mistake and maybe even a poorly implemented feature.

    but I have little sympathy because - well his HD could have crashed or a crypto-worm or... basic data loss could have occurred.

    However - how'd we all learn this lesson? Let others stumble before us or put our own finger in the fan !!!

    1. Re:The lessons of BACKUP !! by bluefoxlucid · · Score: 3, Funny

      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.

    2. Re:The lessons of BACKUP !! by Anonymous Coward · · Score: 0

      Hell even shadow copies would have saved him. Our file servers run shadow copies every 4 hours because our users are too stupid to know not to randomly delete important files and folders and they won't let us revoke delete rights. We are restoring things from shadow copies literally every day.

    3. Re:The lessons of BACKUP !! by hey! · · Score: 1

      What I can't understand is why Microsoft has never gotten its act together and put out a truly modern filesystem.

      Very few people ever come close to using up their disks these days, so why not copy-on-write? Or at least build some kind of versioning into the filesystem.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    4. Re:The lessons of BACKUP !! by Anonymous Coward · · Score: 0

      I think you are out of date. Microsoft built journaling in the first version of NTFS, back in 1993. And it supports file history since NTFS 5, released in the Windows XP timeframe, in 2001.

      Copy-on-write is not a good idea, because it worsens fragmentation and reduces speed, but it could be implemented as an option (I think I have read it is available in ReFS, NTFS' successor introduced in Windows 8, but I'm not sure).

    5. Re:The lessons of BACKUP !! by Anonymous Coward · · Score: 0

      By default Windows eats up the entire HDD, so it makes sort of sense...

    6. Re:The lessons of BACKUP !! by John+Allsup · · Score: 1

      One HD crash are no excuse for losing data. Having your entire IT setup infested with malware is no excuse for losing all but the most recent data.

      In electrical engineering there are various kinds of 'isolators'. These isolate one system from the damaging effects of something going wrong with a neighbouring system.

      Not isolating your work from potential sources of failure is just asking for it.

      --
      John_Chalisque
    7. Re:The lessons of BACKUP !! by hey! · · Score: 1

      Journaling isn't the same thing. The previous versions feature is by default disabled and isn't fs-based -- it requires an external disk of some sort. It's pretty amazing that they've added so much BS to the operating system over the years and haven't got this working.

      ReFS surely a step ion the right direction, but is currently a work in progress. It also lacks snapshotting capability.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    8. Re:The lessons of BACKUP !! by Anonymous Coward · · Score: 0

      Well it has had shadow copies for many versions (require more expensive version) that gives a light version
      On the other had it has had a backup client for years and still his files wasn't backed up so him not having shadow copy on is not suprising.

      But the answer to your question is that its a feature that few "regular" users want and the others who do are willing to pay for it.

    9. Re:The lessons of BACKUP !! by Billly+Gates · · Score: 1

      Look up volume shadow copy? With Windows 7 you can make a volume snapshot and revert back to it.

    10. Re:The lessons of BACKUP !! by Anonymous Coward · · Score: 0

      Very few people ever come close to using up their disks these days, so why not copy-on-write?

      They have that. https://en.wikipedia.org/wiki/Shadow_Copy

    11. Re:The lessons of BACKUP !! by hey! · · Score: 1

      That's a clunky service that barely suffices to back up in-use files. It's not a filesystem feature.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    12. Re:The lessons of BACKUP !! by hey! · · Score: 1

      Not the same thing at all. It's basically for making backups to external drives.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    13. Re:The lessons of BACKUP !! by Anonymous Coward · · Score: 0

      Or at least build some kind of versioning into the filesystem

      There is versioning support in NTFS: https://en.wikipedia.org/wiki/Shadow_Copy

      But of course it's easier to bash Microsoft as if they're idiots and haven't solved this already, right?

    14. Re:The lessons of BACKUP !! by nullforce · · Score: 1

      Like ReFS? https://en.wikipedia.org/wiki/...

      "Resilient File System (ReFS),[4] codenamed "Protogon",[5] is a Microsoft proprietary file system introduced with Windows Server 2012 with the intent of becoming the "next generation" file system after NTFS."

      "ReFS was designed to overcome issues that had become significant over the years since NTFS was conceived, which are related to how data storage requirements had changed. The key design advantages of ReFS include automatic integrity checking and data scrubbing, removal of the need for running chkdsk, protection against data degradation, built-in handling of hard disk drive failure and redundancy, integration of the RAID functionality, a switch to copy/allocate on write for data and metadata updates, handling of very long paths and filenames, and storage virtualization and pooling, including almost arbitrarily sized logical volumes (unrelated to the physical sizes of the used drives)."

    15. Re:The lessons of BACKUP !! by Billly+Gates · · Score: 1

      Yeah. Windows is behind in that area for sure. They never recovered fromt he failed WinFS filesystem which was supposed to have this in Longhorn.

      FreeBSD with ZFS is amazing to say the least

    16. Re:The lessons of BACKUP !! by hey! · · Score: 1

      Yeah, that's exactly what I was thinking. All that ransomware baloney -- if people used XFS their data would all still be there.

      Of course there are situations where you do want to be able to lose data.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    17. Re:The lessons of BACKUP !! by Anonymous Coward · · Score: 0

      no, shadow copy also allows for file versions in the file system, however a retard like this that using real data he has no backup of to experiment with options he doesn't understand isn't going to have enabled that either.

    18. Re:The lessons of BACKUP !! by Anonymous Coward · · Score: 0

      it does not require an external disk at all and can provide basically the same features as journalling. Most users would be pissed if journalling was on by default chewing up disk space.

    19. Re:The lessons of BACKUP !! by gravewax · · Score: 1

      they have had their act together for 5 years now. ReFS is included in all current versions of Windows. Mind you even if he was using ReFS this fuckstick still wouldn't have bothered turning on copy on write as someone that thinks backups, source control or understanding what basic programming tool features do is unnecessary isn't going to do that either. Some people only learn through repeated knocks to the head and this guy sounds like he still needs a few more to beat the stupidity out of him.

    20. Re:The lessons of BACKUP !! by ripvlan · · Score: 1

      yes - well I too have cursed at many a hammer for bashing my thumb. After a long imitation of Yosemite Sam - I quickly realize that maybe the person operating the hammer was at fault.

      But more importantly I don't take to twitter to complain about the "stupid" hammer. Unless I intend it solely in jest of my personal stupidity.

      From the ashes maybe a new OS feature will arise. Something that makes backing up data easier. Seriously - it is harder than it needs to be. Plus I must be an active participant.

  29. God help you by Anonymous Coward · · Score: 0

    You're proficient enough as a programmer to run a project with north of 5000 files, and you don't know the basics of setting up: a file versioning system, a bare metal recovery backup system or just a dumb daily file synchronization job.

    Based on this I'm assuming any sort of repository system is esoteric for you.

  30. This is a story?!? by Anonymous Coward · · Score: 0

    What did he think discard meant?

    Most programs in Windows, other than Windows itself, delete files without putting them in the recycle bin.

    1. Re:This is a story?!? by Anonymous Coward · · Score: 0

      Apparently you yourself think it means something else, otherwise you'd have wrote "discard files without putting them in the recycling bin" instead of reverting to delete.

      Depending on context of the moment, I'd assume it meant to either discard any active changes made and revert to the files, or discard inclusion of the files in the current project. If they meant delete I'd expect delete.

      Disclaimer: I'd also have a few dozen backups, because there is something to be said about trusting assumptions :P

    2. Re:This is a story?!? by Anonymous Coward · · Score: 0

      Yeah, no. Visual Studio uses Git now.

      As in many other Git clients, "discard pending changes", actually discards, well, pending changes. If you've never checked anything in, then everything you have in your folder is a pending change. So don't discard them! As other people have remarked, that's why there's a big warning dialog box that says, "This is IRREVERSIBLE!"

  31. Sorry joshtops by Anonymous Coward · · Score: 0

    Third party submissions are transparent

  32. Been There by ioev · · Score: 2

    Normally I use gitg, but for some reason on one project it wasn't working correctly so I was using VS Code to do the commits. I have definitely highlighted a couple of files and clicked discard rather than stage by accident. Luckily I still had them open in Sublime Text, so I could just undo and save them again, but still, would be nice if this were harder to do.

    1. Re:Been There by shutdown+-p+now · · Score: 1

      It prompts you if you want to discard, both for single-file operation, or for "Discard all changes" that he did. In the latter case, it tells you exactly what it is going to do, with screaming caps for emphasis.

  33. hahahaha by Anonymous Coward · · Score: 0

    This loser calls himself a developer? Like seriously, if you lost that much work just go do a sector by sector file recovery. 5000 files and zero backup? dude! News flash, yes it is easy to delete all those files with just a couple clicks. I've "shift deleted" many files by accident because I got into the habit of bypassing the recycle bin. I'm not about to blame Microsoft.

  34. Wait... by roc97007 · · Score: 3, Insightful

    > f*ck whoever implemented this option

    Probably the same guy who put "logout" in tiny text right next to "restart", also in tiny text, in Windows Server 2012, making every logout of production systems a test in fine motor skills. I'd really like to speak to that person for a few minutes.

    But Dude. Seriously. Backups? If your stuff is important, you need to keep a copy somewhere the computer can't touch it. You are demonstrating a rather naive trust in computer technology, which a seasoned software developer should not have.

    --
    Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
    1. Re:Wait... by Anonymous Coward · · Score: 0

      Good thing no one in IT has ADHD!

    2. Re:Wait... by Neuroelectronic · · Score: 1

      Little UI gotchas like this seem to be purposeful. Diablo 3 has a nice little feature where if you're not accurate you can delete your inventory. BTW inventory in Diablo is worth real money. Oops you deleted your project? should have used OneDrive!

    3. Re:Wait... by Anonymous Coward · · Score: 0

      shutdown -l; make a shortcut already

    4. Re:Wait... by Pascoea · · Score: 1

      At least they have the nag screen that makes you specify why you're shutting down/rebooting before it actually reboots. But not having a minor heart attack when closing every RDP session would be awesome, it's not like horizontal lines and a little padding are expensive.

    5. Re:Wait... by VocationalZero · · Score: 1

      Selecting restart prompts for a reason for the restart on Server 2012. No way to accidentally restart unless your hand is spazzing out or something.

    6. Re:Wait... by roc97007 · · Score: 1

      Good thing no one in IT has ADHD!

      Yeah, good thing adhd isn't common in IT professionals.

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
    7. Re: Wait... by tangent · · Score: 1

      > Probably the same guy who put "logout" in tiny text right next to "restart", also in tiny text, in Windows Server 2012, making every logout of production systems a test in fine motor skills ...or Format right next to Eject on the removable media context menu.

      One prevents the OS from molesting your data, the other ensures it.

    8. Re:Wait... by scdeimos · · Score: 1

      We put a Logout shortcut on all our server desktops to avoid such a problem - not that we RDP to them very often. Thank goodness for PowerShell.

    9. Re:Wait... by Anonymous Coward · · Score: 0

      > Probably the same guy who put "logout" in tiny text right next to "restart", also in tiny text, in Windows Server 2012, making every logout of production systems a test in fine motor skills. I'd really like to speak to that person for a few minutes.

      Really? Seems shutdown -l versus shutdown -r are a hell of a lot more explicit than dicking about with the gui.

    10. Re:Wait... by Anonymous Coward · · Score: 0

      I make a shortcut of logout to the public desktop with the same icon for all production servers. If logout is wrong action, then I do a shortcut to tsdiscon or whatever the correct action is.

    11. Re:Wait... by Anonymous Coward · · Score: 0

      Actually on Win2012 it is the same as Windows 10, The place you logout is totally different from where you restart/shutdown/etc. So not sure what you are thinking about,.

    12. Re:Wait... by roc97007 · · Score: 1

      Right click on lower left corner, observe that logout is right above shutdown.

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
  35. Deadbeat? by El+Cubano · · Score: 1

    d*******

    deadbeat?

    1. Re:Deadbeat? by Gravis+Zero · · Score: 1

      d*******

      deadbeat?

      it's "dipshit" you d*******! ;)

      --
      Anons need not reply. Questions end with a question mark.
    2. Re:Deadbeat? by Binestar · · Score: 1

      By my reckon, it's "dhunter2".

      --
      Do you Gentoo!?
    3. Re:Deadbeat? by El+Cubano · · Score: 1

      That is only seven letters.

    4. Re:Deadbeat? by Gravis+Zero · · Score: 1

      That is only seven letters.

      Arg! If those d[ihpst]{6}s used regular expressions you wouldn't get d[bhimust]{7} mistakes like that! You also may get much better at the Daily Jumble. ;)

      --
      Anons need not reply. Questions end with a question mark.
    5. Re:Deadbeat? by Anonymous Coward · · Score: 0

      d*******

      deadbeat?

      it's "dipshit" you d*******! ;)

      Hey. Don't call GP a dumbass!

  36. Recuva by Anonymous Coward · · Score: 0

    It's fairly easy to recover files off of NTFS on a local drive. If this guy (I'm going to call him king asshat) would have actually taken the time to ask for help instead of ranting he might have got that advise.

    Must be a slow news day though. Play stupid games like clicky click win stupid prizes

  37. Are you sure you want to discard? by Anonymous Coward · · Score: 0

    He's probably a Windoze guy who is used to getting the "are you sure you want to " popup every time he tries to do anything. This time, it sounds like the popup didn't happen. Oh well......

  38. Keep calm and file carve by Anonymous Coward · · Score: 0

    Everyone has accidentally removed something they need at least once. The key is that unless you are actively destroying the data by overwriting it, it's all still there, waiting for you to put it back together.

    The basics are as follows:

    1) Stop what you're doing and don't write any new files to the filesystem because they might overwrite things you care about

    2) Create a full copy of the raw block device

    3) Get to work searching through the disk image for known pieces of your files

    My advice would be to use a linux live environment to piece everything back together, but that's because I am more comfortable with the tools (dd for the disk copy, od and grep for the searching). I'm sure it's equally possible in windows, but I can't offer any pointers.

  39. Big Red Button by jtara · · Score: 5, Funny

    "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...)

    1. Re:Big Red Button by Nutria · · Score: 1

      But we want to nuke North Korea!! (Too bad it's so close to places we care about...)

      --
      "I don't know, therefore Aliens" Wafflebox1
    2. Re:Big Red Button by pubwvj · · Score: 2

      Makes me wonder why you didn't keep a backup copy of North Korea... Anything I value highly I keep backups of, preferably multiple backups of, preferably multiple off-site backups of.

      I guess the data wasn't valuable.

      And no, South Korea is not a backup of North Korea. That's a different version fork.

      (I used to do data recovery long ago in another millennium. After recovering someone's data I would (try to) teach them to keep backups. There was one lady who lost her thesis three times. Each time she would have me recover it. I asked her why she doesn't follow my nice instructions about making backups. She replied, "Why do I need to make backups? I've got you. You'll recover it for me." Some people think differently.)

    3. Re:Big Red Button by Anonymous Coward · · Score: 0

      But we want to nuke North Korea!! (Too bad it's so close to places we care about...)

      If only it were closer to the White House...

      Captcha: godhead

    4. Re:Big Red Button by Tablizer · · Score: 1

      God has a backup in his multi-verse forks, but won't share the password with humans. Although, I hear somebody found an old version of Uranus using the password "Covfefe".

    5. Re:Big Red Button by Anonymous Coward · · Score: 0

      And fuck you, dolphin and whale!

    6. Re:Big Red Button by antdude · · Score: 1

      President DJT, is that you?

      --
      Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
    7. Re:Big Red Button by pubwvj · · Score: 1

      XYZZY often works too...

  40. Hmmm. by Anonymous Coward · · Score: 0

    Another satisfied Microsoft customer!!!

  41. Lulz by Anonymous Coward · · Score: 0

    Funny shit

  42. Developer learns the value of Backups. by DalM · · Score: 1

    Alt Headline.

    1. Re:Developer learns the value of Backups. by JoeCommodore · · Score: 1

      Also developer learns lessons most other developers leaned in their career. Ive lost weeks, probably a month of work now and again - happens. Sometimes you have an old backup - it still stings.

      Well, when you rewrite you probably have some better wisdom now on choosing method A or B, and can code a more efficient replacement, thats the way I think of it.

      Also makes me think of John Harris' struggle with the Atari 8-bit Frogger from Sierra On-Line. (read the complete tale in Hackers by Steve Levy) He had it done and had it stolen (along with all all his 5.25 disks including utilities, etc.) at a programmers convention. No backup, had to re-code it from scratch.

      --
      "Enjoy what you're doing! If it becomes drudgery, you're doing it wrong!" - Jim Butterfield
  43. Was an accident waiting to happen by CraigCruden · · Score: 3, Informative

    It could have been just as easily a drive failure that deleted all the data. Instead, it was discarding the changes (and keeping the original version - which in this case amounted to nothing) [my guess not having familiarity with the tool]...

    I have lost a few hours of changes, but I it would be difficult to lose 3 months. You can use free services such as BitBucket for a single committer/project (private repository) as your offsite source control copy. You should also make a local backup and keep a regular offsite backup for important work that you cannot afford to lose. The fact that you get 3 months into a project then start thinking about source control is utter stupidity. It is a lesson this developer will hopefully learn (even if he has to learn it the hard way). On the bright side -- the second time I do something... it is always quicker...

    1. Re:Was an accident waiting to happen by Pascoea · · Score: 1

      +1 on BitBucket. Saved my ass a number of times. And source control/version control if not for anything other than "what the hell did I change two months ago", in addition to "shit, I just deleted my whole project"

    2. Re:Was an accident waiting to happen by Anonymous Coward · · Score: 0

      [my guess not having familiarity with the tool]...

      That's a harsh lie on the "intuitive!" promise, no?

      I mean, that's the whole shtick that redmond sells its crap with. NO TRAINING NEEDED! INTUITIVE!

      Turns out that if you're not careful, and redmond isn't, then your words belie your assumptions, and that can cause horrific clashes with someone else's "intuitive" assumptions. Like here.

      Guy thought he was just throwing out the management extras that make up a redmondian "project", program took it to mean "and delete all the rest too". Which, er, well, could've been communicated better, in so many ways it's not funny. So it's a pretty bad user interface fail. Saying "user lacks familiarity" is really the wrong thing to say. Especially for this environmnet, especially for the marketing claims of this vendor.

      Of course, the guy should've had backups. That doesn't excuse this massive, massive user interface fail.

  44. Ridiculing idiots = good by Tailhook · · Score: 3, Insightful

    The flaw in vscode should have cost this guy no more than a day or so worth of work. The fact that in this case the consequence of the flaw was the loss of three months of work is entirely the his fault.

    I recommend he ask for his money back and then learn about revision control tools and source repositories and why competent people use them.

    --
    Maw! Fire up the karma burner!
    1. Re:Ridiculing idiots = good by smithcl8 · · Score: 1

      VSCode is free.....that money back isn't going to get him anywhere. :)

    2. Re:Ridiculing idiots = good by Pascoea · · Score: 1

      I think that was the joke.

    3. Re: Ridiculing idiots = good by Anonymous Coward · · Score: 0

      Clearly, trying out new tools on a code base with three months of uncommitted changes and no backups was... how to put this delicately? Well, it was fucking stupid.

      That said, if I lost even a day's worth of work on account of poor/confusing UX, I would be pretty livid.

    4. Re:Ridiculing idiots = good by Anonymous Coward · · Score: 0

      VS Code is free.

    5. Re:Ridiculing idiots = good by Anonymous Coward · · Score: 0

      VS Code is free.

      And Poe's law is a thing.

    6. Re:Ridiculing idiots = good by Anonymous Coward · · Score: 0

      Whether it cost him 1 day or 1 year of work is immaterial - given the scenario it should not have cost him anything. Of COURSE he was a fool for not committing his code frequently but that doesn't mean he did not have a valid point.

    7. Re:Ridiculing idiots = good by Anonymous Coward · · Score: 0

      Even with a "permament" delete this should have taken no more than a day to recover since source code is just text files. Even free hard drive recovery tools can fish those back out.

  45. File recovery is not an option? by Anonymous Coward · · Score: 0

    Why is file recovery not an option?
    Ubuntu live CD + ntfsundelete should be able to recover the deleted repository. If that doesn't work, there are professionals who do that kind of stuff.
    And in the future make sure your code repository is being backed up.

  46. Commit Often by alancronin · · Score: 2

    I think the real question is - why was he working with a local repository / local changes for three months? You commit often so this does not happen.

    1. Re:Commit Often by Anonymous Coward · · Score: 0

      A good system isn't simply version control but includes automatic offsite backups with automatic backup space management and tests. This way even if the version control system blows up somehow, there's atleast 1d/w/m/y interval backups.

      Version control does just what it says, a complete backup solution includes things like write-only/read-only toggle and physical procedures. For a sole person this is more critical than version control to have. Version control is just to make life easier with the work, not a disaster prevention system. If someone had all their stuff in github and no backup that's not good in my book as the backup operators job (you if it's your personal files) is to ensure there's no "eggs in one basket" .. or "eggs in one company" situation. Also it's critical to have a safes where partial keys to decrypt the backups are stores. eg. I forgot my password to my backups. If I had the password in the safes and only had to add a short pin to the password, it would have been practical to recover as long as the safes were accessible.

      I actually also lost the usb stick with the encrypted backups. I did foresee this happening so I had a copy of them on hdd. But that hdd failed. And I still don't recall the password. Thankfully I still have my latest version behind different password so all is good and this all was a good lesson in backups.

  47. Dumbass by Anonymous Coward · · Score: 0

    This is why version control is the first thing you set up on any project. Who in their right mind sits on 3 months of work without making a commit or a backup? If the hard drive had failed he'd be bitching about how the manufacturer sucks. The fact that he "didn't think it was possible" for a Windows machine to lose data tells me this kid should step away from the compiler permanently.

  48. Idiot doesn't backup his work for three months. by Anonymous Coward · · Score: 0

    Details at 11.

  49. Bitbucket and 3 copies minimum by CraigCruden · · Score: 5, Informative

    A single copy on Dropbox that has no SLA with you... is not sufficient.

    You can setup a free account for a private repository on Bitbucket (free for small teams of ... one). (offsite cloud backup).

    You should also be doing regular local backups and rotating them at a friends house as well (3 copies minimum).

    1. Re:Bitbucket and 3 copies minimum by nedlohs · · Score: 3, Insightful

      It depends how important it is. There are many things I would be perfectly satisfied with increasing the "I lose this" chances from "I lose my local copy" to "I lose my local copy and dropbox loses it at the same time". None of those things are my livelihood of course.

    2. Re:Bitbucket and 3 copies minimum by Anonymous Coward · · Score: 0

      Personally I use Timemachine on the Mac, keep everything in Dropbox Pro and use github. That's enough redundancy for me.

    3. Re:Bitbucket and 3 copies minimum by chipschap · · Score: 1

      I backup to the cloud and then replicate to two other computers, just in case there is a cloud problem.

      If your work is important and you care about it, you won't take chances with it.

    4. Re:Bitbucket and 3 copies minimum by roc97007 · · Score: 1

      > You should also be doing regular local backups and rotating them at a friends house as well (3 copies minimum).

      I do this. Raw drive stuck in one of those toaster-like USB boxes. Make a copy overnight of my entire data disk, verify it the next day, and then pull it the hell out of the box so the computer can't scribble on it. At earliest opportunity, deposit it in my friend's fire safe. He doesn't live far enough away to be geo-secure, but at least it's safe from fire.

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
    5. Re:Bitbucket and 3 copies minimum by aktw · · Score: 1

      If your work is serious enough to warrant an SLA with your backup provider, it's probably not a great idea to store copies "at a friends house."

    6. Re:Bitbucket and 3 copies minimum by david_thornley · · Score: 1

      A backup is a copy that won't go away for the same reason as the primary copy. A cloud provider is unlikely to fail or screw up or drop your account at the same time you lose your primary copy. Depending on what you're doing and how safe you want your stuff to be, it might be just fine.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    7. Re:Bitbucket and 3 copies minimum by Anonymous Coward · · Score: 0

      Because github/bitbucket do have SLA with you...

      Um...

    8. Re:Bitbucket and 3 copies minimum by Drethon · · Score: 1

      I had a number of files on copy.com when I found out deleting the parent of my local folder for copy.com, before disconnecting it, blew away all of the files stored online. And given I wasn't the owner of the account I had no access to undelete. Fortunately the most vital stuff was also backed up elsewhere but was not particularly thrilled, taught me that one local backup + online backup may not always be sufficient when the online version auto updates.

    9. Re:Bitbucket and 3 copies minimum by nedlohs · · Score: 1

      If it auto updates it is not a backup. It is just a really slow RAID...

    10. Re:Bitbucket and 3 copies minimum by Gussington · · Score: 1

      A single copy on Dropbox that has no SLA with you... is not sufficient..

      Depends on your requirements. You have the original copy, a local zip backup, and an online zip backup, and historical backups every few days both local and remote.
      That would be sufficient in most DRP's I've worked on.

    11. Re:Bitbucket and 3 copies minimum by dbIII · · Score: 1

      A third party can screw up and not tell you about it until you need the thing. You'll probably learn that lesson the hard way some time.

    12. Re:Bitbucket and 3 copies minimum by RockDoctor · · Score: 1

      At earliest opportunity, deposit it in my friend's fire safe. He doesn't live far enough away to be geo-secure, but at least it's safe from fire.

      RTFM on that "fire safe" to find out just how safe it is from fire. It's probably better than "sitting on the desk", but it's not necessarily going to survive even a house-not-destroying fire.

      Thermal protection requires mass and insulation outside that mass. Both require volume. Volume requires money.

      --
      Birds are not dinosaur descendants;birds are dinosaurs, for all useful meanings of "birds", "are" and "dinosaurs"
    13. Re:Bitbucket and 3 copies minimum by roc97007 · · Score: 1

      At earliest opportunity, deposit it in my friend's fire safe. He doesn't live far enough away to be geo-secure, but at least it's safe from fire.

      RTFM on that "fire safe" to find out just how safe it is from fire. It's probably better than "sitting on the desk", but it's not necessarily going to survive even a house-not-destroying fire.

      Thermal protection requires mass and insulation outside that mass. Both require volume. Volume requires money.

      It's a fairly large, expensive safe, with a high fire rating. (Friend is an IT professional who is a stickler for these things.)

      But that doesn't matter, because I was talking about the data being safe from fire at *my* house. As, his house is far enough away that it's highly unlikely that a single fire would destroy both houses. A natural disaster might, but probably not a fire.

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
  50. Backups? Revision Control? by sizzlinkitty · · Score: 1

    If you didn't use revision control and failed to make backups of your important data, I have no sympathy for you. How do you fail at common sense and be a good developer?

  51. Usually takes Unix by painandgreed · · Score: 2

    Ya, it usually takes UNIX to do something like that. I remember one job, I was given and account on the company application and told I was an admin so I could fix the problems that we had just discussed. The boss then told me to get in there and look around. One of the choices was Email, so I went into email as the application had it's own email system (which as not attached to the outside world so it was just used for internal communication). Then I was greeted with 8 or 9 options such as Read Email. So I read my email of which there was already 30 or so, but most were just department wide things and only a few were actually addressed to me. I got out of the Read function and noticed that down below was Delete All Email, right above Create Email Folder. I thought that I could get rid of most of what was spam anyway, so I hit Delete All Email. It asked "Do you want to Delete All Email?" and I said yes. It then said "Deleting Email ...Deleting Email ...Deleteing Email" and went on for quite some time. Then the phone calls started coming in. Seems that option was to delete all email on the server, not just my own. Only admins get that option, of which I was one. I felt bad even though my boss had been telling people not to use that system for quite some time. I felt a little less bad when another newbie did the exact same thing two years later.

    1. Re:Usually takes Unix by ckatko · · Score: 1

      What is it about software design that 99% of software user interfaces have zero actual thought put into THE USER USING THEM. (Including my !@$!ing new car's "smart" lcd radio.)

      (Almost?) no other professional field could get away with such stupidity:

      "Hey, I made this gun. It's awesome. Best gun ever. But we never actually tested someone firing the gun. It just sat and a test-stand the whole day. So when you go to fire it, the gases explode into your face and blind you."

    2. Re:Usually takes Unix by Anonymous Coward · · Score: 0

      (Almost?) no other professional field could get away with such stupidity:

      Sadly, you are wrong. I know of at least one expensive piece of equipment that positioned an exhaust vent so that it blew hot air directly onto a metal handle. Turn it off, pull it out, sear your flesh. Someone got paid a lot of money to build that and even more to redesign it.

    3. Re:Usually takes Unix by Anonymous Coward · · Score: 0

      "Hey, I made this gun. It's awesome. Best gun ever. But we never actually tested someone firing the gun. It just sat and a test-stand the whole day. So when you go to fire it, the gases explode into your face and blind you."

      It doesn't actually work that way. They do test it, but it's really easy to accidentally learn the weird kinks and quirks you're accidentally building into the system since you're the one continually "testing" it (in a very limited way). So the devs themselves know how to use it by heart, to the point that they completely overlook what's immediately obvious for anyone else trying to use it.

      It's like understanding pointers: Some get it, some just can't, and they never make good programmers. Some people can detach themselves from their own biases and at least accept for the sake of argument that other people have different habits than them, and walk through the design with those different user assumptions. Some can do that fine, and some... just never make good UI designers.

      But to ferret out the quirks, you have to test it, test it, and test it again, using other people than yourself. If you don't, this sort of crap completely blind-sides you later on.

      Apple typically does this much better. Not only have they a rigid design guide with well-defined meanings for various functions (starting with apple-{C,V,X} consistently appearing wherever you can copy/paste/cut), they also religiously do hallway testing. Just grab a couple people not on your team and sit them through your program. Don't help them, jot down whatever goes wrong and see how they try and get around, then fix the program.

      It's something that redmond just... completely does not understand, so you get crap like this.

    4. Re:Usually takes Unix by Anonymous Coward · · Score: 0

      I gave you a "+1 Funny" because it was. I don't see that as necessarily a Unix "bug", but I get your drift.

    5. Re:Usually takes Unix by Anonymous Coward · · Score: 0

      Bad UI design there.

      The best one I did, back around 2002 on a Tru64 Unix box - lucky it was on a test system, an rm -rf ~/ to reset someones home directory for them, except put a space in the wrong place I think and it started rm -rf /, when the prompt didnt come right away I was like uh-oh... ctrl c, ctrl c, ctrl c, ctrl c, ctrl c, ctrl c, but it was too late most of the file system had been hosed along with the system. Went and got the Tru64 install CD, and yesterday backup tape, quickly learned how to boot an Alpha box from CD, reinstalled the OS and dumped the last backup tape over it with the native vdump command, and everything was back to how it was the night before. The only side effect was it hawked the licensing for the Unidata application it ran, which one of the software devs fixed up the next day. Since then I always triple checked, sat back and checked a 4th time before running anything as the super user. What is scary is I could have made this mistake on the live production system just as easily.

    6. Re:Usually takes Unix by Anonymous Coward · · Score: 0

      damn it /. stop eating angle brackets. The command I had intended to run was rm -rf ~some_users_dir/ which I foobared and it interpreted it as rm -rf /

  52. Re:Data Loss by Anonymous Coward · · Score: 0

    Discard isn't delete. I wouldn't have assumed discarding would erase everything, or I'd have to buy new playing cards every poker night.

  53. I played around with rm -rf and it deleted ... by Anonymous Coward · · Score: 0

    ... all my files!!!!

    dude. get a life

  54. Good work ethic by Anonymous Coward · · Score: 0

    Anyone pause to consider that 5000 files in 3 months is not a bad work rate. Could all be crap quality but just saying.

    1. Re:Good work ethic by SecurityGuy · · Score: 1

      Anyone pause to consider that 5000 files in 3 months is not a bad work rate.

      Counting files as a measure of productivity is terrible. Don't do that.

  55. 3 months no backups... of course blame the dev. by CraigCruden · · Score: 1

    It is the developer's responsibility. It is him who did not have a proper backup plan in place. Who else is to blame... it could as easily been a drive failure. It could have been a break'in and stolen computer equipment. It is an expensive less to learn... but hopefully learn he will.

    1. Re:3 months no backups... of course blame the dev. by networkBoy · · Score: 5, Insightful

      to add clarity (and my $0.027)
      It is *absolutely* the developer's responsibility, but *not* his fault.

      The software in question really shouldn't do something this drastic without a second window saying "This will erase files from disk. Are you sure you intend to do this?"

      --
      whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
    2. Re:3 months no backups... of course blame the dev. by sheph · · Score: 1

      Exactly. My first thought was "you're testing a tool that you're not familiar with, using production data, and you didn't make a backup first???" I'm not fond of changing the meaning of discard, but he still should have been more diligent.

      --
      I don't believe in karma, I just call it like I see it.
    3. Re:3 months no backups... of course blame the dev. by Anonymous Coward · · Score: 0

      I disagree, it is TOTALLY his fault. What 'sane' person would test a new product that they have never used before on the ONLY copy of their source code?

    4. Re:3 months no backups... of course blame the dev. by KingMotley · · Score: 5, Insightful

      The software in question really shouldn't do something this drastic without a second window saying "This will erase files from disk. Are you sure you intend to do this?"

      It did actually. He said it came up and warned him "are sure to discard all the changes?" (his words) and he clicked yes. Since he hadn't ever checked anything in, his changes were what he had done in the past 3 months.

      No backups, no source control for 3 months, a guy who doesn't know what source control is or does, and just clicks on warning messages without understanding them is his fault. Regular backups would have saved him. Actually using source control would have saved him. Reading the damn prompt and actually being sure before clicking "Are you sure" would have saved him. Another prompt asking are you really really sure isn't going to save him from himself.

    5. Re:3 months no backups... of course blame the dev. by Anonymous Coward · · Score: 0

      Childish to point fingers. There were a consequence, and the person who could have minimized potential damage is .... ?

    6. Re:3 months no backups... of course blame the dev. by gweihir · · Score: 1

      Amateurs will do amateur things that cause damage to them. So surprise at all. He has only himself to blame.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    7. Re:3 months no backups... of course blame the dev. by Anonymous Coward · · Score: 0

      Normally when software says "discard changes" it means not saving to disk, for example when you close notepad without saving first. It is confusing, but no excuse for not taking a few minutes to make proper backups.

    8. Re:3 months no backups... of course blame the dev. by Anonymous Coward · · Score: 0

      All the possible things that can go wrong:
      power failure causing drive failure
      system update knackers the OS
      misconfigured "clean" option on Makefile does an rm on $(SRC) $(HEADERS)
      misconfigured git,svn or other SCCS options

    9. Re:3 months no backups... of course blame the dev. by modmans2ndcoming · · Score: 1

      lol....it is his FAULT for testing a feature without backups.

    10. Re:3 months no backups... of course blame the dev. by david_thornley · · Score: 1

      If you leave your car unlocked and someone steals your laptop from the passenger seat, it really is the fault of the thief. You've been sufficiently stupid that your insurance company probably won't reimburse under any policy, but I don't think it's your fault.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    11. Re:3 months no backups... of course blame the dev. by Calydor · · Score: 1

      I'm sorry, but to me, 'Discard changes' basically means, "I changed my mind, I don't want to save this structure within this program, but leave the linked files ALONE. Stop touching them right this instant!"

      --
      -=This sig has nothing to do with my comment. Move along now=-
    12. Re:3 months no backups... of course blame the dev. by Anonymous Coward · · Score: 0

      I disagree, it is TOTALLY his fault. What 'sane' person would test a new product that they have never used before on the ONLY copy of their source code?

      ^^^^^THIS^^^^^^^ 1 million times THIS!!!!

      It doesn't matter about the semantics of "discard". He was stupid enough to point software he had never used before at the only copy of his source code.

    13. Re:3 months no backups... of course blame the dev. by Pulzar · · Score: 1

      If you leave your car unlocked and someone steals your laptop from the passenger seat, it really is the fault of the thief.

      How about if you open the door and tell the thief that you'd like all your stuff discarded? And then the thief asks you if you're sure that you want *all* your stuff discarded? And you say, yes, of course.

      Is it still not your fault?

      --
      Never underestimate the bandwidth of a 747 filled with CD-ROMs.
    14. Re:3 months no backups... of course blame the dev. by Anonymous Coward · · Score: 0

      If he has never checked anything in ever then those changes are EVERYTHING. don't make excuses for bad practises and user stupidity.

    15. Re:3 months no backups... of course blame the dev. by Anonymous Coward · · Score: 0

      so funny. I had three months of work, no backups and then started playing with a new version control system. That's some grade A incompetence right there. My favorite is still svn, very simple and not as convoluted as Git and you just run backups on the repository. Integrates in windows with TortoiseSVN, so very Easy peasy.

    16. Re:3 months no backups... of course blame the dev. by Anonymous Coward · · Score: 0

      I wonder if he just didn't commit for 3 months.

    17. Re:3 months no backups... of course blame the dev. by terjeber · · Score: 1

      If you leave your car unopened, and some dude comes over and says: "I'm going to take your laptop now. This theft is going to be IRREVERSIBLE (he shouts the last word). Are you sure you want to leave your car unlocked and have me run off with your laptop?" and you answer - "sure, go right ahead", then it is your fault.

    18. Re:3 months no backups... of course blame the dev. by terjeber · · Score: 1

      This is git, it's not an editor. If you don't understand what git is asking you, then you should be really careful. I have been in a similar situation where there was a warning message with something similar to an all-caps "IRREVERSIBLE" in it. What I did then was to realize that I had probably fucked up in some way or another, and that something bad was going to happen. So, what did I do? I left the warning dialog alone, didn't hit yes, no, ok nor cancel. I left it alone. Then I switched to my command prompt, and I did a complete backup of the directory in which I was working. Finally I switched back to my tool and pressed cancel.

      The guy was a moron, plain and simple. He shouldn't be allowed anywhere near a development environment. Ever. Not because he fucked up. We all fuck up at times. Not because he didn't take a backup, that is also a problem we all sometimes have (though, three months...). He should be kept off all development teams and environments because when he fucked up he blamed someone else who was not even close to guilty.

      People who can't take responsibility for their own fuckups should never work in development.

    19. Re:3 months no backups... of course blame the dev. by Anonymous Coward · · Score: 0

      And they have already stated in this thread "discard" in git isn't delete. Changing semantics is what was wrong here.

  56. Hmm let me see... by tomxor · · Score: 1

    So you have on copy of unversioned files... you plonk them in a new VCS that you know nothing about, you try out commands of unknown purpose and you expect anyone to feel sorry for you?

    Even if this was a decent VCS like git and you git inited a project and then proceeded to use the checkout command without understanding what it does you would have the same problem or git clean or git reset --hard etc etc... if you don't know what it does why are you operating on your only copy. If you haven't learned your lesson yet you are in for a whole life of pain.

    1. Re:Hmm let me see... by Anonymous Coward · · Score: 0

      Hate to break it to you, but Git *is* the default VCS for Visual Studio Code (as in most of the other non-'enterprise' Visual Studio clients these days). This silly person simply didn't know that, if you've never checked anything in, "discard", well... discards all your files. :)

  57. question by shentino · · Score: 5, Funny

    Is it ok if we call this developer a git?

    1. Re:question by hey! · · Score: 1

      For not using git, yes.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    2. Re:question by Anonymous Coward · · Score: 0

      Like I replied to the comment above yours, Git *is* the default VCS for Visual Studio Code (as in most of the other non-'enterprise' Visual Studio clients these days). This silly person simply didn't know that, if you've never checked anything in, "discard", well... discards all your files. :)

    3. Re:question by Anonymous Coward · · Score: 0

      He WAS using Git, that is actually the problem, he was using a tool he didn't understand (VS Code uses git)

  58. Backups backups backups... by ErichTheRed · · Score: 1

    Everyone says "I really should back this up" until they need it. I don't even heed my own advice half the time and have been burned horribly over it. This guy's lucky he just lost his own files -- I've found it's way too easy to pave over cloud-based stuff by just issuing a command on the wrong set of resources -- the API and script-based access method is nice and fast, but totally de-nerfed in some situations. If you have the access, it's just going to do what you tell it.

    That said....user interfaces can be horribly confusing too. It's one of the downsides of this super-fast deployment cycle; no one tests usability the way they tested a fully released, boxed product.

    1. Re:Backups backups backups... by Billly+Gates · · Score: 1

      Not to mention he wanted "to play".

      When I do this I make a copy or play with a test project. Lord help him if he has to go into System Administration after he losses his job over this. I have a raid 0 on my system. Dangerous? YEP. But it is fast as hell for goofing around with virtual machines. Do I have anything critical? Nope ISO files are on oldschool mechanical disks and so is software storage. My documents are on a regular disk and backup up to a cloud solution. If it fails? Beh. Just rebuild the raid 0 and the VM's as I got all the important things on more reliable storage. As a computer operator owner here more people ...especially TECH people ... should do proper care and maintenance just like with their cars.

  59. Maybe next time read the instructions first? by Anonymous Coward · · Score: 0

    "...and I was just playing with the source control option, seeing how it wanted to stage ..."

    Randomly clicking buttons you think should do something doesn't mean they always do.

    Sounds like a lesson learned the hard way, but not the fault of the software.

  60. No backups - no sympathy. by Anonymous Coward · · Score: 0

    The headline should have been - Ignorant programmer who "trust me, I know computers" ignores all good advice and doesn't have backups of his work.

  61. Commodore 64 in 1983... by MindPrison · · Score: 3, Interesting

    ...taught me to back up my stuff.

    I remember when I spent my first "programming" hours, at the tender age of 12, painstakingly typing in the program examples in the manual, just to withness the power cord glide out of the mains plug entirely without my help. It happened twice in a row (I got a new computer later on, it was a factory defect).

    But that taught me to always back up my stuff. I remember often making 5-10 backups of my machine language experiments on the C64, this is a habit that has followed me into the modern age.

    I think that's testimony to our times, things work so well that people don't experience losses before it's too late, so they don't feel the natural need to protect their stuff.

    --
    What this world is coming to - is for you and me to decide.
    1. Re:Commodore 64 in 1983... by Anonymous Coward · · Score: 0

      I had the same problems with Windows 95 crashing. I now have an obsessive compulsion to Ctrl-S several times a minute, save to multiple backup files, and wave the cursor around while anything is processing to see if the computer froze.

  62. Re:Who approved this "story"? by Nutria · · Score: 1

    Maybe he approved it for the sole purpose of giving us an opportunity to laugh at and mock eliecerthoms (who has subsequently deleted his github account).

    --
    "I don't know, therefore Aliens" Wafflebox1
  63. Dumbass Accidentally Deletes 'Three-Month' of Work by Anonymous Coward · · Score: 0

    fixed the title for you

  64. Loser by Anonymous Coward · · Score: 0

    What a pathetic loser

  65. your fault by matushorvath · · Score: 2

    Learn to use proper source control. Learn to back up. Learn not to experiment with new tools on the single copy of priceless data.

  66. developer - a meaningless word by kiviQr · · Score: 1

    People used to have a good understanding of how computers work, network, reliability, etc. Now everyone types 'git init .' and thinks that they are doing source control management.

  67. Re:Translation by Anonymous Coward · · Score: 0

    Because "democrat voice" and "democrat hands" actually means something.

    You're ridiculous.

  68. hints by kiviQr · · Score: 1

    A couple hints: RAID0, backup, git push/svn commit.

    1. Re:hints by Anonymous Coward · · Score: 0

      RAID0 makes you more susceptible to data loss than JBOD.

    2. Re:hints by Anonymous Coward · · Score: 0

      raid 0!? i think you mean raid 1 or raid 5.

    3. Re:hints by Thanatiel · · Score: 1

      RAID 1 or 10, never 5 again.

      --
      Irrelevant news and morons using moderation to mod down what they disagree on. 2018 resolution: so long.
    4. Re:hints by Anonymous Coward · · Score: 0

      Ah--dumbshit.
      If you hit delete on a RAID array, the data are deleted.

      Note to DumbShit - RAID IS NOT BACKUP.

    5. Re:hints by Anonymous Coward · · Score: 0

      i get all except RAID0 which would have made the situation worse in this case and trades resilience for speed.
      And no amount of RAID would have saved him since RAID is for availability not backup

  69. Overwriting at same time you crash your drive? by CraigCruden · · Score: 1

    And what happens if you overwrite the copy in Dropbox just as your system crashes? (not familiar with Dropbox edge cases). Bitbucket is free, it is easy... and it is more suitable.

    1. Re:Overwriting at same time you crash your drive? by sexconker · · Score: 1

      You go to dropbox.com and recover the previous version.

      I don't know how many previous versions you can recover or how far back you can go on the free version of dropbox, but I know it works.

    2. Re:Overwriting at same time you crash your drive? by Anonymous Coward · · Score: 0

      I'm not advocating using Dropbox in place of proper version control, BUT... Dropbox has the ability to restore deleted files and even keeps revision history letting you roll back a file to any point in the past. You could (but not should) put a git repo inside your Dropbox folder, and in an event like this, Dropbox could restore everything VSC deleted.

    3. Re:Overwriting at same time you crash your drive? by KingMotley · · Score: 1

      What is the SLA on bitbucket? Do they refund your monthly $0 if they crash and lose all your data?

    4. Re:Overwriting at same time you crash your drive? by war4peace · · Score: 1

      How often did they crash since their inception?

      --
      ...gis sdrawkcab (usually not responding to ACs; don't bother posting as AC)
    5. Re:Overwriting at same time you crash your drive? by Anonymous Coward · · Score: 0

      I use dramatically different source management/backup/revision/recovery systems on the mission-critical product that my team maintains vs the one-page site that I created to host a streamable version of my daughter's school play.

      Different tools for different purposes.

    6. Re:Overwriting at same time you crash your drive? by Calydor · · Score: 1

      How often did Dropbox crash?

      --
      -=This sig has nothing to do with my comment. Move along now=-
    7. Re:Overwriting at same time you crash your drive? by KingMotley · · Score: 1

      Twice?

    8. Re: Overwriting at same time you crash your drive? by Anonymous Coward · · Score: 0

      Unlimited (afaik) versions for 30 days.

  70. Re:Who approved this "story"? by Anonymous Coward · · Score: 0

    Maybe because it seems to blame "another badly designed Microsoft product"? Surely, this could never have happened with Linux, which protects the stupid user from typing "sudo rm -rf /"...

  71. A wise man once told me... by internet-redstar · · Score: 3, Insightful

    A wise man once told me: "If it isn't worth to be put in git, then it's not worth to be written". Guess he was right ;-)

    1. Re:A wise man once told me... by Anonymous Coward · · Score: 0

      I use Mercurial, you insensitive clod!

    2. Re:A wise man once told me... by Anonymous Coward · · Score: 0

      That code is needed to run the Springfield nuclear power plant!

  72. Sigh. by ledow · · Score: 1

    Hey, "developer".

    Shadow Copies.

    And back your shit up.

    Rather than relying on Recycle Bin.

    1. Re:Sigh. by Anonymous Coward · · Score: 0

      Rather than relying on Recycle Bin.

      While I'm mainly a UNIX guy when I do use Windows I do so 100% command line for file manipulations. I guess I never developed that "Recycle Bin" security blanket. It's a bad one.

      On that note, a developer should know better than to trust a computer.

    2. Re:Sigh. by ledow · · Score: 1

      I don't see why anyone relies on it.

      Shift while deleting deletes without the recycling bin.

      Almost all programs that "delete" do so bypassing the recycling bin.

      The command line knows nothing of the recycling bin.

      When the disk is full, or the recycling bin hits quota, it gets emptied.

      Network drives do not have a recycling bin.

      It's the worst possible place to use, expect or rely on.

      On all my networks, I disable it to stop people relying on it. It doesn't work on their (default home) network drives anyway.

      Shadow copies (basically filesystem snapshots) gives you a safety barrier for EVERY file on the drive with some of the same kind of caveats but at least it's transparent to applications - they don't need to support it for it to work. It also works on network drives, and you can restore several versions of files and entire folders or drives, or even cherry-pick an old revision of a file and copy it without having to rollback to it.

      But here, it's complete apathy for file safety. No backups, and let's just use my files rather than a copy of my files.

  73. Next lesson by fahrbot-bot · · Score: 1

    Experiencing the joy of:

    % rm * .o
    rm: .o not found

    I think it's hardwired -- or "baked in" if you will (ya, I read the iOS 11 Has a Feature To Temporarily Disable Touch ID thread :-) -- into my DNA at this point to check for white space when typing commands like this before hitting Enter.

    --
    It must have been something you assimilated. . . .
    1. Re:Next lesson by Anonymous Coward · · Score: 0

      Had a manager do that from the root. Deleted most of the system files before he cancelled out. The system continued to run. I realized that I could go get the backup tapes and restore the root. Users never noticed a thing, manager kept his self-respect. Got laid off later because the department was going to a "real" computer (mainframe). Department disappeared later because the application was no longer "profitable".

  74. Troll? by farble1670 · · Score: 0

    Okay, I guess this is a troll? We're supposed to comment how stupid he is for not using source control and backups now?

    1. Re:Troll? by Baron_Yam · · Score: 1

      Stealth advertising; in a few days or a week or so, maybe we will see an article about a wonderful new repository system, and this post will have primed us to absorb it.

  75. Just tried it by Zalbik · · Score: 5, Informative

    So just for fun, I tried it.

    Did he happen to ignore the popup with the big yellow exclamation mark that says:
    "Are you sure you want to discard ALL changes? This is IRREVERSIBLE!"

    At the very least the ALL CAPS WITH EXCLAMATION MARK! should have possibly made him think "Hmmm...this seems to be a pretty important question"

    But apparently he decided: "Ah, screw it. It's only 3 months of my life".

    Given that level of skill, I can't think much of importance was lost.

    1. Re:Just tried it by jm007 · · Score: 1

      wow, the missing piece to complete the puzzle

      thank you, sir, nothing more needs to be said

      that's a wrap!

    2. Re:Just tried it by StormReaver · · Score: 3, Insightful

      Did he happen to ignore the popup with the big yellow exclamation mark that says:
      "Are you sure you want to discard ALL changes? This is IRREVERSIBLE!"

      It's perfectly reasonable to interpret that prompt as meaning, "all changes since my last commit." It's a really bad prompt, and should never have been allowed into the program.

    3. Re:Just tried it by Anonymous Coward · · Score: 0

      that's a pretty stupid dialogue. "Changes" is not usually defined as "5000 files saved over the preceding 3 months."

    4. Re:Just tried it by Anonymous Coward · · Score: 2, Insightful

      I think you missed the fact that 'discard all changes' is what he wanted. But it didn't discard all changes. Discard all changes would've undone everything since the moment he last saved or opened a file'. These files were imported into the software, not created there. So the discard state should've been untouched files, not empty the entire directory tree.

      Is the fact that he has no backup hilarious? Oh yes it was. But is this an issue that needs to be fixed? Yes. Most definitely.

    5. Re:Just tried it by Anonymous Coward · · Score: 0

      its easy to interpret his last commit as the fucking code he just committed to the system

    6. Re:Just tried it by PmanAce · · Score: 3, Interesting

      He never did an original commit so all changes since "last" commit is everything, just like you said.

      --
      Tired of my customary (Score:1)
    7. Re:Just tried it by jtara · · Score: 2

      It's perfectly reasonable to interpret that prompt as meaning, "all changes since my last commit."

      And that's exactly what it would have done.

      Had he made any commits.

    8. Re:Just tried it by ilctoh · · Score: 2

      The fact that the operation is irreversible is clear enough. That fact that "all changes" is actually synonymous with "every file, regardless of whether or not you think you've actually CHANGED it" is not.

      --
      How many slashes would a slashdot dot, if a slashdot could dot slashes?
    9. Re:Just tried it by elistan · · Score: 2

      "Are you sure you want to discard ALL changes? This is IRREVERSIBLE!"

      I certainly blame the victim for not having backups. But given the wording here, I don't blame them for not realizing that this would delete everything. I guess the import deleted the source as everything was being imported, after which the files were in a pending state, and the discard then deleted the pending files without putting them back to the source prior to the import...? Or maybe the import process marked the files as "these belong to me now" inside of VS, with a pending status, and the discard is programmed to delete pending files regardless of how they became pending? Either way, that sounds like a flaw with the program not VS. Of course, perhaps during the import process there's some big red warning saying "This import process marks all files as pending and does not preserve the source of the files, so discarding these files will erase the source you are importing from unless you commit them."

      Disclaimer: not a VS user.

    10. Re:Just tried it by Anonymous Coward · · Score: 1

      No, this is definitely VS' fault. When you type junk into Notepad and try to close the program, it asks you "Are you sure you want to discard these changes?" And everyone chooses "Yes" because they want to discard junk data. So that's what he did.

      The dialog box should've said. "Are you sure you want to DELETE all your files?"

    11. Re:Just tried it by elistan · · Score: 1

      a flaw with the program not VS.

      Sorry, meant to say "a flaw with the program not the user/victim."

    12. Re:Just tried it by Anonymous Coward · · Score: 0

      How does this make a difference? His last commit was the state three months ago and it deleted any changes.
      What else would you expect?

    13. Re:Just tried it by Anonymous Coward · · Score: 0

      Unfortunately, as the user wrote:

      "I hadn't commited any of them to any repository."

    14. Re:Just tried it by Anonymous Coward · · Score: 0

      It does mean since last commit. He had no commits so it discarded everything.

    15. Re:Just tried it by argStyopa · · Score: 1

      I'm wondering if the "issue" had more to do with a missed deadline for a customer than an actual problem with the software...

      --
      -Styopa
    16. Re:Just tried it by Anonymous Coward · · Score: 0

      And since there were 0 commits, that means all changes.

    17. Re:Just tried it by Anonymous Coward · · Score: 0

      If he did this, you can imagine the quality of those 3 months of work.

    18. Re:Just tried it by thegarbz · · Score: 1

      all changes since my last commit

      That's exactly what it means and exactly what it deleted.

    19. Re:Just tried it by Anonymous Coward · · Score: 0

      Well, as I've mentioned elsewhere in this thread, *Git* is the default version control system (VCS) for Visual Studio Code (as in most of the other non-'enterprise' Visual Studio clients these days).

      So this person didn't know how to use Git, and didn't realize that "discard pending changes", actually discards, well, pending changes. If you've never checked anything in, then everything you have in your folder is a pending change. So don't discard them! (As other people have remarked, that's why there's a big warning dialog box that says, "This is IRREVERSIBLE!")

      Look, I feel bad for the person who lost some work. But Git, even though it's the world's most popular VCS, is a power tool. And as Linux people will tell you, you shouldn't attempt to use power tools (even through Visual Studio Code) without Reading The Friendly Manual.

    20. Re:Just tried it by Anonymous Coward · · Score: 0

      As I've mentioned elsewhere in this thread, *Git* is the default version control system (VCS) for Visual Studio Code (as in most of the other non-'enterprise' Visual Studio clients these days).

      So this person didn't know how to use Git, and didn't realize that "discard pending changes", actually discards, well, pending changes. If you've never checked anything in, then everything you have in your folder is a pending change. So don't discard them! (As other people have remarked, that's why there's a big warning dialog box that says, "This is IRREVERSIBLE!")

      Look, I feel bad for the person who lost some work. But Git, even though it's the world's most popular VCS, is a power tool. And as Linux people will tell you, you shouldn't attempt to use power tools (even through Visual Studio Code) without Reading The Friendly Manual.

    21. Re:Just tried it by Anonymous Coward · · Score: 0

      Discard changes, not delete you files you moron.

    22. Re:Just tried it by gravewax · · Score: 1

      Did he happen to ignore the popup with the big yellow exclamation mark that says: "Are you sure you want to discard ALL changes? This is IRREVERSIBLE!"

      It's perfectly reasonable to interpret that prompt as meaning, "all changes since my last commit." It's a really bad prompt, and should never have been allowed into the program.

      yes it is perfectly reasonable to interpret it as that and surprise surprise that is exactly what it does mean. The guy was a moron that had never committed a change therefore everything was disguarded. This is the behaviour I would expect and most developers would expect.

    23. Re:Just tried it by shutdown+-p+now · · Score: 1

      This is a "Discard all changes" button on a tool pane that is labelled "Source Control: Git". Discarding state in this context, quite obviously, means going back to the last commit in the repo. Which is exactly what it did.

    24. Re:Just tried it by StormReaver · · Score: 1

      He never did an original commit so all changes since "last" commit is everything, just like you said.

      That's an awful interpretation. If there was no original commit, then NOTHING should have been deleted. Again, VS Code did something horrendous.

    25. Re:Just tried it by terjeber · · Score: 1

      How would you word it? It does exactly what it says. It's also not really VSCode, it's Git. One of the things we some times need in Git is to reverse all changes made since the last commit, so the feature needs to be in VSCode if it is to integrate properly with Git. Should MS remove this Git feature from VSCode?

      I agree that software should try to make morons not do moronic things, but development tools should not assume that its users are brain dead fools. This would make the development tool impossible to use for developers, who you have to assume are not computer illiterate. VSCode with massive warnings at several levels would be a source of frustration for all users.

      Should a compiler also refuse to compile software that might, for example, erase the entire $HOME directory of a user? Again, this is a developer tool. It should stay out of the way as much as possible, and assume I am not a moron.

    26. Re:Just tried it by terjeber · · Score: 1

      No, VSCode didn't do anything at all, Git did, and Git did exactly what the user asked Git to do.

    27. Re:Just tried it by terjeber · · Score: 1

      Disclaimer: not a VS user.

      Clearly also not a Git user, since this was Git, not VSCode. Now, if you ever start using Git, here's a few ways not to be a moron. 1/ Read a little about Git first. 2/ Don't start using it on production code if you have no clue. 3/ Do backups.

      The guy was a moron and this was only his fault. If he has problems with what happened he should take them up with Linus Thorvalds, and I am not sure he'd come away from that entirely unscathed.

  76. He... by Tsolias · · Score: 1

    Clicked discard and it deleted all his files. Ppl here claim that this was the most probable and normal outcome....welp let's see, how many ides or editors do that....none, except the stupid vs. The usual terminology dictates delete/erase for such actions, and discard is used when you want to revert to some default options. Anyway, play with stupid software, win stupid prizes.

  77. How is this news??? by Selur · · Score: 1

    Why is this here?

    1. Re:How is this news??? by Anonymous Coward · · Score: 0

      To ensure that nobody hires this schmuck for a development position. Ever.

  78. That expression is not performant by Anonymous Coward · · Score: 0

    n/t

  79. Reminds me of the McDonalds hot coffee suit. by Anonymous Coward · · Score: 0

    Reminds me of the McDonalds hot coffee suit.

    Bad or intentional design ruins things as well.

    Not just blaming the user.

  80. Pulitzer Prize post ! by gosand · · Score: 2

    A random guy posts a rant on MS github page, gets 8 responses, and it becomes a story on Slashdot?

    Some days I really question why I still read this site.

    --

    My beliefs do not require that you agree with them.

    1. Re:Pulitzer Prize post ! by Gussington · · Score: 1

      A random guy posts a rant on MS github page, gets 8 responses, and it becomes a story on Slashdot?

      Some days I really question why I still read this site.

      This is the only comment that needs to be here. Fuck Slashdot.

    2. Re:Pulitzer Prize post ! by Anonymous Coward · · Score: 0

      The story itself is a small piece of nothing. And yet it's spawned 700+ comments including some very informative sub-threads.
      The story content is irrelevant; the topic is very important.

  81. HAHAHAHAHAHAHA by Anonymous Coward · · Score: 0

    What a maroon.

  82. Really? by superdave80 · · Score: 1
    FTFS:

    A developer accidentally three-month of his work.

    IT'S THE FIRST SENTENCE!!! DO YOU NOT READ YOUR CRAP?

    1. Re:Really? by Anonymous Coward · · Score: 0

      I think they were trying to be cute. Why bother with the article? The description says it all--with zero sympathies given.

    2. Re:Really? by Anonymous Coward · · Score: 0

      Apparently you didn't the memo.

    3. Re:Really? by freeze128 · · Score: 1

      It's so meta... He deleted the word "deleted".

  83. Nice lesson by Anonymous Coward · · Score: 0

    7 copies, unlinked. 3 local, 4 offsite as many places as you can get them.

    1. Re:Nice lesson by Pascoea · · Score: 1

      7 seems excessive... But I agree with the sentiment.

  84. Bitbucket & git push by Anonymous Coward · · Score: 0

    Seriously? a simple git push would solve all his issues. it sux but I bet you won't make that mistake again (unless you blame the IDE for your lack of knowledge about vcs ... in which case it most definitely will happen again)

  85. What a twat by Anonymous Coward · · Score: 0

    No backups = no sympathy. No backups for 3 months = inexcusable.

  86. SVN by JBMcB · · Score: 3, Informative

    To be fair, I was using an old version of subversion, and issued a delete to a particular project branch I was working on. I deleted the project from that branch, and every other branch, along with every version. From everywhere. Not what I wanted. Not even what I asked. Turns out it was a bug triggered from upgrading the app on the specific platform I was on (I think it was Cygwin?)

    I had another machine with an old trunk that I recovered from, but still, crap like that happens even with source control.

    --
    My Other Computer Is A Data General Nova III.
    1. Re:SVN by F.Ultra · · Score: 3, Informative

      A delete in svn does delete the local files but the files are still there in the repository, a delete is basically a flag for the file there. If it where very old version of svn there might even been a local copy left in hidden .svn folders all over your project folder full with the old files.

    2. Re:SVN by Anonymous Coward · · Score: 0

      As a release engineer who has been using subversion since The initial release I have to disagree with this statement. You cannot delete anything from a subversion repository without exporting the repository, creating a new repository, and then importing the dump while filtering out what you want to have deleted with the svndumpfilter command. The "delete" function is merely deleting the contents from the current revision. It still exists in previous revisions which can be undone by simply copying the branch from an earlier revision where it existed or performing a reverse merge from the revision that caused the erroneous delete. Commits only create new revisions and do not alter existing revisions.

    3. Re:SVN by Anonymous Coward · · Score: 0

      Even beyond that, SVN (unlike git) doesn't even provide a way to irretrievably delete data, so it's simply impossible for it all to have vanished as a result of *any* action taken by the client.

    4. Re:SVN by david_thornley · · Score: 1

      Yeah. If you want to delete anything from a svn repository, you serialize the repository to a readable form, remove what you don't want, and put what's left back into what's essentially a new repository. (Or have they finally implemented the -obliterate subcommand that spent so much time on the bug list?)

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    5. Re:SVN by Anonymous Coward · · Score: 0

      It looks like you just discovered that svn does not have real branches or tags. It was one of the major regressions from CVS and RCS that preceded it, and I was never convinced that the limited implementation of atomic commits in svn was worth the loss of features.

      If you checkout a subtree of the repository, then deleting probably would have done what you expected, but if you checked out the full repository and used your local filesystem to navigate the branches, then it would act like you described.

      Crap like that happens with crappy source control. If you'd been using git and somehow managed to do the same thing through misguided forced pushes, your other machine would have been able to push the entire repository history, not just the most recent version of trunk to recover.

    6. Re:SVN by F.Ultra · · Score: 1

      Don't think they have:

      f.ultra@ubuntu:~$ svn help | grep obliterate
      f.ultra@ubuntu:~$

    7. Re:SVN by JBMcB · · Score: 1

      The bug had to do with the revisions, IIRC (this was ~12 years ago), was particular to the Windows port, whichever one I was using (mingw or cygwin I can't remember) and only showed up when upgrading from one specific version to another, as the internal versioning structures had changed. I probably ran a cleanup after the delete, which nuked the (now) un-versioned files from the filesystem.

      --
      My Other Computer Is A Data General Nova III.
  87. Only two words... by lucaiaco · · Score: 1

    git gud.

  88. Good!! by EvilSS · · Score: 1

    Cannot even find them in the Recycle Bin!!!! I didn't even thought that was possible on Windows!!!

    If you don't even know enough about the OS you are developing on to understand stuff like this, I'm glad your work got wiped out to spare the people who would run it the torment to come.

    --
    I browse on +1 so AC's need not respond, I won't see it.
  89. Developer? Sure? by williamyf · · Score: 3, Insightful

    From The Sumary:

      "I had just downloaded VScode as an alternative and I was just ***playing*** with the source control option"[emphasis mine]

    So, you are a ***profesional*** "developer"?
    And you ***play*** with three months worth of important-non-backed-up stuff?
    Without RTFM?

    Sorry, but IMNSHO, that dude is a MORON (all caps intended).

    If you do not believe me, RTFA. I know that is not customary on /. but just try, is quite short...

    I know that bashing all things microsoft is fashionable on ./ (I've done so a few times myself), but this making front page is a new low in clickbait by the editors...

    --
    *** Suerte a todos y Feliz dia!
    1. Re:Developer? Sure? by Anonymous Coward · · Score: 0

      I know that bashing all things microsoft is fashionable on ./ (I've done so a few times myself), but this making front page is a new low in clickbait by the editors...

      I got one username for you: msmash

  90. Not a story here... by Sigma+7 · · Score: 1

    Maybe it's a story on The Daily WTF.

    Developers always need a backup, even if it's something as simple as a manual synchronization between two computers.

  91. This guy was working 3 month on the same files?! by CustomSolvers2 · · Score: 1

    When coding, I start working on a fresh set of files (make a copy of folder "1", rename to "2" and continue working on it) various times per day (it depends upon the complexity/importance of the development) and automatically duplicate the last set. And, in case of being particularly difficult/important, I store another copy in an external drive. I backup all relevant folders almost daily. Around twice a month, I do an external backup of my whole hard-drive.

    Once, I made a mistake while doing the first backups and lost a whole hour of work. It was a horrible experience which I expect to never pass through again... And this guy loses 3 months of work in one click!! H*ly shi*! There aren't enough asterisks in the world to express so much pain. LOL.

    --
    Custom Solvers 2.0 = Alvaro Carballo Garcia = varocarbas.
  92. Developers strike again by smooth+wombat · · Score: 3, Insightful

    It's funny, every time I mention how bad software is I get modded down. Not necessarily any particular software, but software in general. Between clunky interfaces, having to go spelunking to find what you want, bloat, you name it, software today is not a pleasure to work with.

    Now this person, a developer in their own right, is complaining about another developer(s) who apparently couldn't see their way to not destroy file.

    Welcome to my world, where every day it's a war to try and find solutions to the incompetence of software developers.

    --
    We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
    1. Re:Developers strike again by Anonymous Coward · · Score: 0

      It's funny, every time I mention how bad software is I get modded down.

      Really? Weird. I Have been visiting Slashdot since 1999 and some the most consistent sentiments about software over that time are that it is 99% shit and 99% of developers are incompetent idiots.

      Welcome to my world, where every day it's a war to try and find solutions to the incompetence of software developers.

      That has been my world as working as a developer for nearly 20 years.

      I will grant you one thing -- the only group held in lower esteem on average than developers is users.

    2. Re:Developers strike again by Anonymous Coward · · Score: 0

      See especially server software, especially cryptographic anything.

      The guiding philosophy seems to be, "Thou shalt emit error messages, but they shall not be helpful. As far as possible, thy error messages shalt scream bloody murder that a thing cannot be done, but must never, if it can possibly be helped, reveal why that thing was being done. If thy error message doth actually help the user figure out what is wrong and fix it, thou hath failed."

      One of the biggest realizations on my first big project was: five minutes spent adding robust error reporting can easily save 50 hours single-stepping through gdb... in the wrong section of code. The value of simply running the code and its automatically printing "Here's the exact line, function and file I was in things went pear shaped, and a stack trace for your convenience" is more than its weight in gold.

    3. Re:Developers strike again by bsolar · · Score: 1

      Welcome to my world, where every day it's a war to try and find solutions to the incompetence of software developers.

      Welcome to mine, where every day it's a war to try and find solutions to the incompetence of software users.

    4. Re:Developers strike again by thegarbz · · Score: 1

      It's funny, every time I mention how bad software is I get modded down. Not necessarily any particular software, but software in general. Between clunky interfaces, having to go spelunking to find what you want, bloat, you name it, software today is not a pleasure to work with.

      You think software is bad you should see some of the users. Big warnings, in caps, users don't understand and from the options of "Stop and think and read the manual" or "proceed with thing I don't understand" they choose the latter.

  93. Can't blame the others... by Anonymous Coward · · Score: 0

    ...for your screw-ups. Even if they, too, screwed up.

  94. tough lesson by jm007 · · Score: 1

    let us all bow our heads for a moment of silence... in remembrance of not only our own similar painful experience(s), but of our brethren's; let us mock his ignorance so that he may also one day partake of the joy in knowing the world is chock full of fuckups just like us

    tough lesson, to be sure; took me a couple times of getting burned to bake in redundancies for my project's assets

    that being said, why use a semi-vague term like 'discard' being the nuke option with no clarifications and confirmations? I wonder if it's an ESL issue... you know, not malicious, just ignorant

    1. Re:tough lesson by jm007 · · Score: 1

      replying to my own post....

      true story bro, as I was about to click 'Submit' for some reason I hit refresh instead..... lost the post, dumbass! lolololololol

      but since I had actually composed it in notepad, the backup plan was at the ready: just a re-copy/paste and back in action; would have hated for all y'all to miss my funny informative insightfulness

  95. Try a keyboard by Anonymous Coward · · Score: 0

    Mice are terrible for tasks that require such precision

  96. almost as idiotic as not backing up... by kbdd · · Score: 2

    If your work is important to you, backup and don't use it an an experiment to try new tools. Otherwise, don't be a bitch. I made my case...

    1. Re:almost as idiotic as not backing up... by DRAGONWEEZEL · · Score: 1

      I think my sig says it all.

      --
      How much is your data worth? Back it up now.
  97. In other news a submitter and an editor... by Anonymous Coward · · Score: 0
    In other news the submitter or the editor deleted 3/4 of a second of their typing by posting:

    A developer accidentally three-month of his work.

    They clearly deleted the word "deleted" from the 4th position in that sentence - which may not quite be irony, but is what often passes for it on the Internet.

  98. I clicked discard... AND IT DELETED ALL MY FILES by QuietLagoon · · Score: 2

    Obviously his work was not something that he cared about since he had no backups. So I do not see why he is complaining.

  99. undelete by jupiter126 · · Score: 1

    Happily for the dev, software like that only deletes the files in the partition information, meaning it is possible to recover the data in most cases using some undelete programs. (stuff like https://www.easeus.com/data-re... ) I recommend you use the computer the least possible before recovering the files, as windows might overwrite them if used.

  100. "playing" by go-nix.ca · · Score: 1

    ...and I was just playing with the source control option...

    If you're "playing" with a never-before-tried feature of a never-before-tried program while handing over control of your precious source code to it, you should at least back it up first.

  101. Needs a title fix: by Anonymous Coward · · Score: 0

    Moron proves he's unemployable by showing complete lack of good, let alone best, practices for code handling.

  102. Just recover the files? by Togden · · Score: 1

    I've used a few peices of software that read the blank space on a drive and re-establish everything remotely file like back into the files it was before it was deleted. Surely for a developer this is an obvious solution.

  103. Thank You God by Anonymous Coward · · Score: 0

    I believe that we have been spared from a monstrosity.

  104. Has he ever used Windows? by Anonymous Coward · · Score: 0

    "Cannot even find them in the Recycle Bin!!!! I didn't even thought that was possible on Windows!!!"

    Gotta ask, how did this guy use computers long enough to become a developer and still live under the illusion that Windows puts every deleted file in the recycle bin?

  105. Go get your backups and restore... by bobbied · · Score: 1

    No backups?

    If you cannot be bothered to make regular backups, I cannot be bothered to help you fix your mistakes or feel bad for your plight when something stupid happens.. Get off my lawn you idiot!

    --
    "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
  106. Only apps can app apps! by Anonymous Coward · · Score: 0

    App Studio Code apped three months of LUDDITE work! Only apps can app apps!

    Apps!

  107. Three months without backups? by 140Mandak262Jamuna · · Score: 1
    Shut up and you don't get to complain.

    Messing around with unfamiliar source control system without backups? Get lost. There are lots of serious people with genuine complaints. This one, even I won't blame it on microsoft.

    --
    sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
  108. Better Title by JohnFen · · Score: 1

    "Developer pulls a boneheaded maneuver, loses three months of work"

    Come on, man. No version control? Or, at a bare minimum, not copying your work somewhere else just in case?

  109. You'd think... by DaEMoN128 · · Score: 1

    that someone working on 5k files that represent 3 months of his life would treat them with a bit of caution. In any school I've been to, they talk about save frequently.. because computer errors happen. When I got into IT 20ish years ago and heard of backups, my brain immediately applied that same mentality to it. This guy, whose livelihood may depend on this code.. couldn't be bothered to protect his work? Well, that will weed him out of the employment pool.

    --
    Stop signs are only Suggestions
  110. Thank god - 3 months of bugs erased by Anonymous Coward · · Score: 1

    Based on the level of skill this guy demonstrated, one must assume wiping out 3 months of code saved a lot of people a lot of troubling dealing with whatever gawd awful, bug laden code he was producing.

  111. target audience by smithcl8 · · Score: 1

    While I appreciate the idea that software should be made to keep people from doing dumb things, VS Code is made basically for the developer community. Isn't /. the site where everyone says "RTFM" to people when they screw up? This cat should've known better than to assume...

  112. This is why by Anonymous Coward · · Score: 0

    ...we have been using revision control for, oh, 40 years.

  113. Re:It doesn't even include a compiler! by Spacelord · · Score: 1

    VSCode is not meant to be a full blown IDE. It's an editor, and competes with other editors like atom and sublime.

  114. Git would do the same by Anonymous Coward · · Score: 0

    If you told it to discard all your unstaged changes.

  115. Undelete by Anonymous Coward · · Score: 0

    Instead of using his browser to post comments and keep using his OS for days, he should have installed a undelete utility ASAP on a flash drive from another computer and recovered the files. They're still on the disk, until he accidentally overwrites the blocks that is.

  116. MULTIPLE faults and multiple blames. by Anonymous Coward · · Score: 0

    MULTIPLE faults and multiple blames.

    But they DID change the nomenclature, which is a NO NO.

  117. why does an idiot press discard... by Anonymous Coward · · Score: 0

    then blame everyone else for the program discarding ????

    Oh, and the files are still on the hard drive unless he did anything after he pressed discard. They can be recovered if he did NOTHING after that. He just needs to take the hard drive to a data recovery service, or buy data recovery software. No Big Deal.

    If you know what you're doing. Which he apparently doesn't.

  118. I've Posted This Before by Anonymous Coward · · Score: 0

    Microsoft is the world largest malware supplier.

  119. Git out of here, its great. by TiggertheMad · · Score: 4, Insightful

    A single developer shouldn't be using git.

    Why not? I use it for all my projects, if for no other reason than to not be this guy. If I delete all my local code, its on a server and multiple other systems. it is cheap, simple and keeps everything in sync.

    I have had non-coder friends who have heard about git, and asked if it would work for non-code digital assets. (Pictures, e-books, music, etc).

    --

    HA! I just wasted some of your bandwidth with a frivolous sig!
    1. Re:Git out of here, its great. by darkain · · Score: 4, Informative

      Totally this! I've been coding for some 20 years now or so. Even for small personal projects, they go into a managed repository. I lost about a week's worth of code in my youth, then I learned about Microsoft Visual SourceSafe, their local repository system. Then I transitioned that over to Source Offsite, a networked version of SourceSafe. This progression then moved through the ranks of CVS, SVN, and now to GIT. Having version control has so many benefits for even single devs, like diffing revision history. "How did I fuck myself up? Oh yeah, I can just check my commit history!" - This has saved my ass countless times.

    2. Re: Git out of here, its great. by Anonymous Coward · · Score: 0

      Got merges are still fuckef up . Error messages are written like lazy coders. It's only suited for single user.

    3. Re: Git out of here, its great. by Dog-Cow · · Score: 1

      Got

      That's what you git for using shitty Chinese knockoffs.

  120. Sit coquus conscientiam ... by Anonymous Coward · · Score: 0

    If you're chopping vegetables for a living, I can *tell* you a million times to wisely (1) keep your knife sharp, and (2) curl your fingers.

    But the best way to really learn & internalize that wisdom?

    Lop the end of your finger off with a dull knife! If you're lucky, all it takes is once ...

    xoxo,
        "7-fingers" Bob

    p.s. neither the knife manufacturer, nor your maker have the *slightest* culpability in said emergency-room trip ...

  121. 5,000 source files in 3 months? by Anonymous Coward · · Score: 0

    A novice programmer created 5,000 source files in 3 months for his mega project. Before moving on to other parts of this [non] story, let's just think about that part of it for a moment. That would mean, on average, he was adding 55 source files daily for 90 days. Really? Is any part of this story true?

    1. Re:5,000 source files in 3 months? by cheesybagel · · Score: 1

      Sounds like the typical lamer OO-coder project. All it takes to create a couple of files is to use the IDE to create a new class.

  122. This guy seems the type who would.. by Sqreater · · Score: 1

    ..speculatively try to swap the front and rear tires of his car for a better ride while driving down the highway to his mom's house. Who tries to "play with" new software using critical files in the middle of a project? And NO backups. Anywhere. duh

    --
    E Proelio Veritas.
  123. s/VScode/hard drive/g by bigjocker · · Score: 1

    "I had just installed a new hard drive as an alternative and I was just playing with the cables and it shorted, AND ALL MY FILES WERE DELETED, ALL OF THEM, PERMANENTLY! who the hell is the ****** who made the option to permanently delete all the files on a drive by accident even possible?"

    --
    Life isn't like a box of chocolates. It's more like a jar of jalapenos. What you do today, might burn your ass tomorrow.
  124. It's his own fault by aldousd666 · · Score: 1

    If his hard drive would have just been wiped by a virus he'd be in the same boat. use a remote repo. no excuses.

    --
    Speak for yourself.
  125. Use a disk recovery solution by JohnGeorge5342 · · Score: 1

    Recuva is pretty good, the files staged on disk should still be on the blocks haven't been overwritten.

    1. Re: Use a disk recovery solution by JohnGeorge5342 · · Score: 1

      *Still be there* Damned beer. -J

  126. Damn Microsoft ... by Anonymous Coward · · Score: 0

    ... you have taught them to not be responsable for their actions because the OS and the tools will protect them from themselves.

    That is another point in favor of *NIX: it will not protect you, it will serve you.

  127. Guy's not necessarily a moron by rsilvergun · · Score: 1

    everybody gets tired, has off days, etc, etc. There's over 6 billion of us on this planet. A large software project will have hundreds of users. Mistakes are going to happen. A software versioning tool should never delete all record of code unless the user goes through multiple prompts and hoops. It's astonishingly bad design.

    I think we're way too quick to blame the user (in everything, not just software). Reminds me of Toyota's sudden acceleration problem. People blamed stupid old people for years until a young guy with a manual transmission had happen to him and limped it into the dealer while it was doing it. Toyota was finally forced to admit the caused the problem and fix it.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
    1. Re:Guy's not necessarily a moron by ChoGGi · · Score: 1

      Sure I've off days, but I just restored from backup, and called it an early day.
      Not having a single backup of three months of work = moron.

    2. Re:Guy's not necessarily a moron by jittles · · Score: 1

      everybody gets tired, has off days, etc, etc.

      Wasting mod points to comment here but... Apparently this gentleman had over 90 off days in a row since he had never done a single commit during 90 days and discarded all of his uncommitted changes.

    3. Re:Guy's not necessarily a moron by terjeber · · Score: 1

      everybody gets tired, has off days, etc, etc

      This guy didn't have a bad day, he had just finished three no-brain-whatsoever months. That's not having a bad day.

      A software versioning tool should never delete all record of code unless the user goes through multiple prompts and hoops ... astonishingly bad design

      If you think so, bring it up with Linus Torvalds, but I disagree with you, in fact I think your statement is bloody nonsense. If you can't read a dialog box with the word "IRREVERSIBLE" in it as a strong warning not to do what you are thinking about doing, you're an idiot. If I really want to reverse all changes, I would be livid if the software threw up one dialog after another asking if I was REALLY sure I wanted to do it.

  128. Yeah, no. by Anonymous Coward · · Score: 0

    I don't like microsoft visual studio, but still.
    This is what happens when you randomly click through warnings without reading what it does.

  129. This is a sign of a focused programmer by Anonymous Coward · · Score: 0

    Most programmers are so worried about covering things that can go wrong in the process of coding that they don't actually focus on producing something of value. Maybe if Microsoft had such focus, they could cater to developing better products for focused programmers that won't punish people who actually like to make something of quality.

    But alas, what business nowadays truly wants to be productive?? They'd rather support their employees' social clubs and thoughtlessness at work and pretend like they're not at fault for hurting their own bottom line.

    Well that's what you get for not thinking!! (Apple excluded.)

  130. A Hunch by Anonymous Coward · · Score: 0

    I'm going to out on a limb here, and go with my hunch that this is the same guy: https://medium.com/@thoms/dont-even-bother-with-this-342f229164c0

    Frankly, based on his diatribe, I feel that he probably deserves what he got. He should have made backups, and he should have been proactive. Is it bad design? Sure, but don't be a dumbass, and back up your data!

  131. Piriform Recuva by Anonymous Coward · · Score: 0

    Use a file restorer like Piriform Recuva, think yourself lucky, learn how to use a computer, learn how to use Git, learn how to use VSCode, then grow up.

  132. Learned early by BenBoy · · Score: 1
    He looks like a young man, and this lesson should last him a good long time (once the stinging subsides). Mark Twain put it well:

    ...the person that had took a bull by the tail once had learnt sixty or seventy times as much as a person that hadn't, and said a person that started in to carry a cat home by the tail was getting knowledge that was always going to be useful to him, and warn't ever going to grow dim or doubtful.

    -Tom Sawyer Abroad

  133. GitLab is also good (free) by p4nther2004 · · Score: 1

    Although I'm finally decided to up and pay for an account on Github.

    The rule is simple:
    Work in git
    Work on a feature branch
    git add *
    git commit 'updating'
    git push origin feature/branch

    Oh yeah...and you want to back that puppy up.

    1. Re:GitLab is also good (free) by gnasher719 · · Score: 1

      I have a little app in the App Store, just for fun. There are copies of the source (1) on BitBucket, (2) on Mac #1, (3) on Mac #2, (4, 5) on two Time Machine backups of Mac #1, and (6) on one Time Machine backup of Mac #2. The repos obviously contain all versions, but might get corrupted. If that happens, three Time Machine backups contain all versions of the repos! Effort for this: Zero.

    2. Re:GitLab is also good (free) by macsuibhne · · Score: 1

      +1 for GitLab as well.

      Tony

      --
      -- "Quis custodiet ipsos custodes?" -- Juvenal
  134. deleted files by Anonymous Coward · · Score: 0

    and just because it is not in your recycle bin doesn;t mean the file are gone as in data overwritten ffs. stop. load up recovery software....

    but seriously? no version control? no offsite backups.....

    is this an advert on who not to hire to do a job? or just clickbait / signupbait

  135. Recycle Bin by Anonymous Coward · · Score: 0

    A software developer that doesn't think Windows could delete files without them ending up in the Recycle Bin clearly never used Shift+Delete to delete files in Windows Explorer. Shift delete works just like the Linux rm command: the file is gone. (I don't really care about local files, and Samba on my file server always does a add_counter_and_move_to_hidden_folder when instructed to delete files by Windows, even with Shift.)

  136. Classic: User error by Anonymous Coward · · Score: 0

    Read the manual, use source control and don't blame it on the dog when he eats your home work...

  137. Use TimeMachine by Anonymous Coward · · Score: 0

    Use TimeMachine and your files are back in a minute. Oh wait, he's using Windows.

  138. Git by technomom · · Score: 1

    3 months and it didn't occur to you to use a version control system?

  139. Idiot by allo · · Score: 1

    First testing new features without a proper backup, then no source control or at least no remote repository and then using a lot of swear words against the program, which probably just wasn't used the right way. Okay, maybe the program isn't doing its job very good, but a software developer should have backup and should have backup of his vcs. Seriously, use git and push to a repository on your own server, NAS or just another computer. Here even another repository on the same computer would have saved the work.

    1. Re:Idiot by allo · · Score: 1

      Not only a lot of swear words, but using silly censoring on them as well. The irony ...

  140. Just becaus it was 3 months of work form _him_ .. by Anonymous Coward · · Score: 0

    doesn't mean it wasn't only 3 hours of work for someone a little more clever ..

  141. He needs to do a root cause analyisis by JustNiz · · Score: 1

    I love the way he furiously grasps for anything/everything else to blame but himself.

  142. Slashdot Owners by Anonymous Coward · · Score: 0

    Please remove "msmash" as an editor at Slashdot. This person doesn't have the first clue about technology and posts inflammatory articles as flamebait.

  143. Change the title of the story by Anonymous Coward · · Score: 0

    The story title should be changed to; "Incompetent Developer Accidentally Deletes Three-Month of Work With Visual Studio Code, Whines about it."

    I think this is covered under the old quote: "A poor workman blames his tools."

  144. Re: 3 months no backups... of course blame the dev by Anonymous Coward · · Score: 0

    I'm sure the distinction gives him comfort.

  145. Why is this on /.? by Anonymous Coward · · Score: 0

    This does not belong here.

  146. Maybe he could run a recovery program by Anonymous Coward · · Score: 0

    The whole situation is unfortunate and I can sympathize.

    I would have posted this on the source page, but the thread is closed. This guy may want to try and run a recovery program against his hard drive to see if he can recover his work.

  147. Food for thought by Anonymous Coward · · Score: 0

    "I made a discovery today. I found a computer. Wait a second, this is
    cool. It does what I want it to. If it makes a mistake, it's because I
    screwed it up. Not because it doesn't like me...
                                    Or feels threatened by me...
                                    Or thinks I'm a smart ass...
                                    Or doesn't like teaching and shouldn't be here..."
    [...]

    Maybe the guy shouldn't of been testing a new application (editor) using his important files.

  148. More anti MS BullShit by Billly+Gates · · Score: 1

    I am getting tired of this rhetoric as Slashdot seems to be the I.T. equivalent of FoxNews with a bias. I even submitted a story last week on 'LaTex' now coming to MS Word in Office 365 which is one of the complaints I have read here for 20 years and thought some would be happy to hear. I got marked for Spam??

      If you do not like Microsoft products do not use them. No one if forcing you. But some of us do use them and they are prevalent in the I.T. field

    I bet in Emacs I can delete things too or Eclipse or any other modern environment. Like what others say have a backup and no "online" storage like RAID or cloud solutions ARE NOT BACKUP as you can delete things online. I am not paid by Microsoft, nor am I a fanatic. Infact I used to be heavily anti MS back in the day hence my name. I just want to see rational people and stories for a change!

  149. Incompetent by Anonymous Coward · · Score: 0

    Fire him. Not worth having a guy like that on your team. Doesn't cover his ass and freaks out when HE screws up.

  150. Why not just recover them? by Anonymous Coward · · Score: 0

    Seriously just go recover the files using one of the millions of free tools. Sounds like he has no clue how computers even work.

  151. Moron by Anonymous Coward · · Score: 0

    What kind of moron doesn't have ANY backups for the past three months? The developer in question should be fired.

  152. Hello world. I'm an idiot by Anonymous Coward · · Score: 0

    Let me share a story of just how big an idiot I am. Without any disaster recovery system in place I precipitated a disaster by using a feature without bothering to read what it did. I are a developer.

  153. Proofread by Brockmire · · Score: 1

    Fuck you Slashdot editors. Stop trying to win the title of shittiest editor. Take 1 minute to proofread your garbage. If you don't find at least one mistake, read it again until you do. You don't even need to go past the first sentence. Seriously, how the fuck are you getting paid to be editors? Do you have fucking bosses that are supposed to tell you that your work is unacceptable and need to do basic reading or be fired? For fuck sakes, every fucking story.

  154. JCL by Anonymous Coward · · Score: 0

    LOL i just found out that id you have jcl delete a data member on abend it can delete the entire data set. dont put your output in your cobol source folder
    i had another copy tho ;)

  155. Must be a millenial by modmans2ndcoming · · Score: 1

    He blames everyone but himself for his fuckup and not having a backup. Dumbass.

  156. Recovery tools by angel'o'sphere · · Score: 1

    Unless he created lots of new files, there are recovering tools that basically find all deleted files.
    Assuming he used something like C# the filenames can be recovered from the contents of the file.
    However that does not work for every programming language.

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  157. CryptoWall Pain by Anonymous Coward · · Score: 0

    Oh yeah, I was hit with the CryptoWall virus and lost 25+ years of IP. It's going on two years and I still can't bring myself to touch that computer.

    I feel your pain.

  158. New Low by Anonymous Coward · · Score: 0

    Lord. So a noob made a mistake. If he has a brain, he'll learn something from this.

  159. Oh forf fucks sake by MichaelSmith · · Score: 1

    Commit early. Commit often. Push every commit.

  160. Why by jemmyw · · Score: 3

    Why is this story here? Did the byline change to "News for idiots, they stuffed up"?

  161. Dear Slashdot by Anonymous Coward · · Score: 0

    I once deleted a file by accident too, back in September 1992. It turned out that for some reason that I do not recall the nightly backup had not completed during the preceding night, so the total incompetence of the IT department made me lose two whole days. Fortunately, I had edited only a few lines in this less than 500-line file. Not as impressive as what this guy achieved, but I'll be celebrating the 25th anniversary of this shocking event soon. Can I have a headline too?. That would be so 1337...

  162. he is totally gay by Anonymous Coward · · Score: 0

    Using Microsoft and not taking a backup. How can anyone be so gay?

  163. Re:This guy was working 3 month on the same files? by angel'o'sphere · · Score: 2

    And why don't you use a version control system instead of a set of back up directories?

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  164. Re: Data Loss by Brockmire · · Score: 1

    Dictionary disagrees. "Get rid of...". Should be taken as expect it to be gone. That's the same as delete in my book.

  165. lol by Anonymous Coward · · Score: 0

    vs code is a great editor and holding shift while deleting something is a windows convention for perma-deletion... it is known...

    this guy had a shitty day

    this is news?

  166. put "logout" in tiny text right next to "restart" by Anonymous Coward · · Score: 0

    "Probably the same guy who put "logout" in tiny text right next to "restart", also in tiny text, in Windows Server 2012, making every logout of production systems a test in fine motor skills."

    Anonymoose to keep mods. I wanted to mark it "+1 funny" because it made me laugh, but marked it "+1 insightful" because I've thought the same thing. And I'm an insightful person.

    sr

  167. What a boob by Anonymous Coward · · Score: 0

    What an idiot. He obviously knows nothing about backups or source control. Why the hell would you click DISCARD on something you had no idea what you were using.

    You got what you deserved.

  168. This isnt a total disaster. by Anonymous Coward · · Score: 0

    Take the drive out, put it in another running machine and run "recuva"

    www.recuva.com

  169. Visual Studio is only good for one thing by Anonymous Coward · · Score: 0

    If you want to program in C#, by all means. However, that's about all Visual $tudio is good for and doesn't do Mac and Linux any favors, regardless of the fact that it's also available for them. It's Micro$ofts way of tricking programmers to come back to the dark side. There are plenty of other IDE out there. Learn C and C++ and forget C#; it's nothing more than a programmer prison. You need interface design? Xcode, Glade, Qt Designer, etc. Need an easier way to make games? Unity, Unreal, Godot, or Blender BGE. Need something even lighter than that? Use Geany and a few plugins. I would rather use NetBeans for C for Christ sake.

  170. I'd bet you my right nut by Anonymous Coward · · Score: 0

    nothing of value was lost.

  171. Re:Blaming the victim = good by QuasiEvil · · Score: 1

    The victim is a victim because he's an idiot. Should VSC behave better? Probably, don't know, haven't tried what he did to see if it really does that. Should we really pity in any way, shape, or form some guy with only a single copy of three months worth of work? That just shows a naive, idiotic trust that the world is a big, safe sandbox in which to play and not be accountable for protecting yourself. Which, of course, is completely out of touch with reality.

    Have I nuked my changes before on accident by doing the wrong thing? Yeah, more than I'd like to admit. You know who I blame? The meatbag between the chair and the keyboard.

  172. Amatuer by Anonymous Coward · · Score: 0
    From the link:

    yeah, so the damage done by the destructive bug in the code is now my fault for not being a clairvoyant and seeing this piece of shit software was going to fuck up my files. I don't need to explain why I don't have a private repo with my stuff. It is the software's concern NOT to destroy the integrity of a computer like a damn virus. You come here, see my despair and berate me for something that was not my fault, and has happened to a lot of other people? Fuck you.

    I guess that makes you a complete moron for "trying out a new tool" on something that was "so valuable" to you. You don't have to be clariovoyant. Maybe if it had any value to you there might have been backups taken beforehand, or you would have actually had it all committed to a Git repository and would have been "trying out a new tool" on a fork instead. Git forks are excellent for experiments. FFS, grow the hell up.

  173. Not a developer by Anonymous Coward · · Score: 0

    This is a moron, not a developer. Every programmer knows to backup, backup, and backup. In 40 years of programming I've lost my code once, on my first job due to the cleaning grew splattering hot wax all over my 8" discs that I left on my desk. But all I lost was 1 days work as I learned from my College experience to backup to multiple times, and have backups off-site as well.

    The cloud is okay but not if it can be directly accessed from within your daily routine. This is an example of a poor backup plan. If it is too easy to overlay or delete your backups it isn't a good idea to use it.

  174. How embarrassing... by Anonymous Coward · · Score: 0

    I've never made a mistake this bad, but if I did I wouldn't post about it online so that the whole world could learn of it.

    Also, this guy has a potty-mouth. Hiring managers: please avoid.

  175. Sounds suspect by Anonymous Coward · · Score: 0

    Who has 5000 files in a project?

  176. Missing The Real Story by Anonymous Coward · · Score: 0

    After 3 months working on a project, he had 5,000 files! FIVE THOUSAND FILES. That's 55 new files per day or 2.29 per hour 24x7 for 90 days. WTF was he coding?

  177. Yeah, lay off this kid by Anonymous Coward · · Score: 0

    Is there anyone posting on Slashdot who didn't learn the same lesson the hard way? So pointing their finger at him and mocking him is very douchy.
     
    Yeah he should have backed up and you can bet from now on he will. As for the user interface that's fucked use of terminology by Microsoft. UI's should always be clear and they should always give users a way to recover from otherwise catastrophic actions. People get tired. They fuck up. They push the wrong button. They make mistakes.

    1. Re:Yeah, lay off this kid by Anonymous Coward · · Score: 0

      Again, like I've said elsewhere, *Git* is the default version control system (VCS) for Visual Studio Code (as in most of the other non-'enterprise' Visual Studio clients these days).

      As in many other Git clients, "discard pending changes", actually discards, well, pending changes. If you've never checked anything in, then everything you have in your folder is a pending change. So don't discard them!

      It's not "fucked use of terminology by Microsoft". As other people have remarked, that's why there's a big warning dialog box that says, "This is IRREVERSIBLE!"

      If you click on a warning like that, without thinking for a moment about what files were in the window you were just looking at, then I feel sorry for you. That was a terrible accident, and I hope it doesn't happen again; maybe next time pay closer attention?

    2. Re:Yeah, lay off this kid by MightyYar · · Score: 1

      Is there anyone posting on Slashdot who didn't learn the same lesson the hard way?

      No, that was my sentiment exactly. This guy was going to lose his data. I'm not saying the software is well designed, simply that his lack of backups meant this was inevitable.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
  178. Is this the developer equivalent by Snufu · · Score: 1

    of the Darwin award?

    On the positive side, the world has been spared having to interact with a program written by someone with the professionalism displayed.

  179. Back in the day by Anonymous Coward · · Score: 0

    Back when I was in high school I didn't know what version control was.
    I didn't even know what coding was.
    But when working on school projects I, and every single member of any team I did projects with, always made copies of our word documents.
    We made several copies per day. We stored them on floppies. We put them on USB drives.
    It only took once for someone to wipe out 2 days of work the day before we had to hand in a project for us to realize that everything had to be copied somewhere to avoid accidental destruction.
    It seems like somehow this guy made it through all of school and into the workforce without learning that lesson.

  180. Has he tried an un-delete utility? by Anonymous Coward · · Score: 0

    If he's lucky, he may not have over-written the clusters containing the lost files. He can use an un-delete utility such as this one. Even if he doesn't recover all 5000 of his files, he will at least have recovered some of them.

  181. HA !!! by Anonymous Coward · · Score: 0

    Broken Hard Drive will gave the same result.... virus, cryptoransomware, data corruption....

  182. NPD by Anonymous Coward · · Score: 0

    He looks like to have a narcissistic personality... watch your back

  183. No on MY team by Spinlock_1977 · · Score: 1

    I don't want this person on MY team. Potty mouth.

    --
    - The Kessel run is for nerf herders. I can circumnavigate the entire Central Finite Curve in a lot less than 12 parse
  184. No Backup? by Anonymous Coward · · Score: 0

    Seriously, if developers can't follow best practices, how can we expect our software not to get crappier?

  185. Bitch please, I don't even trust by Anonymous Coward · · Score: 0

    Bitch please, I don't even trust closing my gmail tab after I hit "save draft" until I confirm it saved.
    I open a second tab and check the drafts folder to make sure it's there and correct.

    And if it was a big/important email, I save a copy on my machine and BCC myself because I don't even trust the sent folder to get it or keep it as long as I might need it.

  186. How could this happen? by Anonymous Coward · · Score: 0

    Oh, right, an idiot.

  187. lol by Hugh+Jorgen · · Score: 0

    What a clown. A developer that doesn't commit to source control? Not even a DropBox, OneDrive, Mozy, BackBlaze or bazillion other options. I call bullshit.

  188. Backup Slowly But Surely... by pubwvj · · Score: 1

    Makes me wonder why he didn't keep a backup copy... Anything I value highly I keep backups of, preferably multiple backups of, preferably multiple off-site backups of.

    I guess the data wasn't valuable.

    (I used to do data recovery long ago in another millennium. After recovering someone's data I would (try to) teach them to keep backups. There was one lady who lost her thesis three times. Each time she would have me recover it. I asked her why she doesn't follow my nice instructions about making backups. She replied, "Why do I need to make backups? I've got you. You'll recover it for me." Some people think differently.)

  189. dd is your friend by Anonymous Coward · · Score: 0

    To be fair, the guy sounds like he was trying to get his code under revision control, and VC seems to have done something non-obvious and highly destructive without warning or more reasonably moving files out of the way of a new checkout.

    The may not be visible, but I'd find it hard to believe they were actually zeroed out. Create an image of the disk and run some file recovery

  190. This is why I will never use Linux by Anonymous Coward · · Score: 0

    A similar thing happened to me when I was playing with a Linux VM and tried the DD command with sudo dd if=/dev/zero of=/dev/sdc. What kind of OS lets you erase the the whole fscking hard drive including the boot block? Now I also have to stay away from Windows too?

  191. Hmmm.... by Anonymous Coward · · Score: 0

    At least stop what you're doing and use a utility to un-delete files.

    In this day and age, storage is dirt cheap. He could have even burned a CD or DVD with his source code.
    This sucks, but if there was a hardware failure, he would have been in the same boat.

    Also... 5000 files? That's extremely prolific for 3 months work.
    If this was for a company, he'd be gone.
    If he was a private contractor: the client wouldn't care about excuses and would be right to question his claim.
    If it was his own project: I doubt he did this all on his own time and if he did, he's able to support himself.

    He should at least be a little mad at himself.

    This is my own opinion.

  192. What by JustAnotherOldGuy · · Score: 1

    "A developer accidentally three-month of his work."

    Is there a missing from that sentence?

    --
    Just cruising through this digital world at 33 1/3 rpm...
  193. Any good developer knows... by gnunick · · Score: 1

    ...when starting a new project:

    • Step 1. $ git init # (substitute your preferred VCS flavor)
    • .
    • .
    • .
    • Step n. (At least) by the end of day one: Commit your work (and push it to another drive or server somewhere)

    Unless "three months of work" only means a few days' of actual work, there should have been dozens if not hundreds of commits by then. No excuses.

    Never blame the tool for losing more than a day's worth of work--or it's you who ends up looking like the real tool.

    --
    I have no special gift, I am only passionately curious. --Albert Einstein
  194. Hahaha by Anonymous Coward · · Score: 0

    But don't worry. You're a smart developer who knows how their operating system and hardware work, right? You can recover those files with five minutes of coding, right?

  195. Docs him by Anonymous Coward · · Score: 0

    Name and delete him.

  196. Use a better editor by Anonymous Coward · · Score: 0

    Yes I get the guy is an idiot for not backing anything up for 3 months and or checking his stuff into his version control software.

    That said, better editors do their own backups just for this case. You're not always editing things that are in version control.

  197. The lady needed skin grafts by MrKaos · · Score: 1

    Reminds me of the McDonalds hot coffee suit.

    Bad or intentional design ruins things as well.

    Not just blaming the user.

    Glad you pointed this out. This lady suffered incredible pain that required skin grafts, while the media was humiliating her. Why McD was serving coffee so hot after they had received so many complaints was a mystery and that they required a lawsuit to correct their practices showed how stubborn they were.

    --
    My ism, it's full of beliefs.
  198. It's one of those important learning moments. by Anonymous Coward · · Score: 0

    We all have them and it teaches us about why all that nonsense other people are always banging on about is actually important.

    Next time he'll be more cautious about blythey clicking through messages on system he's unfamiliar with and think "What's the worst that can happen ?" ..and possibly do more backups.

    Unfortunately a lot of software these days ignores the fact that some people are still learning some tech & assumes that the user understands the implications of what they're doing, and what language means in particular context. This often leads to those hash learning moments.

  199. are you fucking serious? by Anonymous Coward · · Score: 0

    Another story of how somone wanted a shortcut without reading or understanding the situation clearly, getting fucked.
    moving ahead, there are several steps to resolve the situation..
    Look for Hirens BootCD there is a tool to find and "UNDELETE" your files with a very high likelyhood of full success
    back up your data
    it could be worse, somehow it could have attached your corp repository then you may be in deeper sheeit...
    but, your not there. so figure how how to fix ur shit and quit your bitching...

  200. Three months! by brausch · · Score: 1

    Who doesn't make a backup in three months? Sorry dude, not much sympathy here.

    --
    "Almost every wise saying has an opposite one, no less wise, to balance it." - George Santayana
  201. VSS by Anonymous Coward · · Score: 0

    Wasn't it possible in VSS at one time for anybody with commit access to roll back the entire repository effectively deleting the entire repo?

  202. Version control?? by Anonymous Coward · · Score: 0

    A "developer" would use version control...

  203. Publish the name by Anonymous Coward · · Score: 0

    So that nobody hires him by mistake.

  204. Bitch at git, not VSCode by LostMyBeaver · · Score: 1

    Ok, the button you clicked is called 'git discard'. VSCode calls git and git discards your changes.

    This is 2017. What in the world are you doing writing code you consider important without knowing how to use git, subversion, mercurial, or a dozen other source control systems.

    I have made a similar mistake to what this guy did. I've lost 2 hours of work because I WAS STUPID and clicked discard in frustration during a merge.

    Let's start with some basics here :
      1) You are a REALLY REALLY REALLY inexperienced programmer.
      2) If you did a lot of work before using a revision control system, you're an idiot
      3) If you knew about revision control and still didn't use it from the moment you created the project, you're a really really big idiot
      4) If you coded for 2 days without using a revision control system, you are a moron
      5) If you didn't create at least one full backup every single day of your code when not using a revision control system then you're not even useful in this world as cannon fodder. I'd recommend considering a long term career as fertilizer, but you'd fuck that up too.
      6) You didn't run Windows Backup and Restore either. See, these are tools like Apple Time Machine. They are free and turned on in 5 clicks. But you're a cowboy right?
      7) You didn't consider mapping the development folder to OneDrive, DropBox or any other place on earth which would make sure you had a backup? Are you seriously here blaming VS code for the loss of your data? Do you practice ballroom dancing in busy traffic intersections while blindfolded and then blame Henry Ford for inventing the internal combustion engine when you get hit by a bus?

    Let's continue with some good stuff here.
        1) You shouldn't be writing code and it's better that code is lost.
        2) The code you wrote was absolute shit. I know this because if you don't know how to not lose code, then it was written by someone who has never written a single useful line of code worth not losing before.
        3) You mention 5000 files. Great... most were documents or auto-generated in some form. I, as a developer who sucks less than you with A LOT of experience write 10,000 lines of code in a month during project startup in a language I'm competent in. That includes inline documentation, readme.md files, design documents and more. Following the first month, I'll probably add another 1-2000 lines a month until beta. So in three months, I may have if I really wrote TONS of rock star shit, about 15000 lines of code. That would be about 3 lines per file in your world. Of course, you are counting processed data or images or whatever as code.

    I would recommend that if you ever plan on trying to code again... you do at least an hour of research, watch some videos on how experienced programmers work. There's a lot more to programming than just typing code.

  205. Disappeared from the web. Name change next? by LostMyBeaver · · Score: 1

    Did anyone notice that this guy who used eliecerthoms as his github handle deleted his account and then also started deleting his entire online profile? He even has blocked his LinkedIn profile from being public.

    I suppose he'll consider a name change next. It certainly might be a good idea at this point.

  206. Re:This guy was working 3 month on the same files? by CustomSolvers2 · · Score: 1

    And why don't you use a version control system instead of a set of back up directories?

    As usual (after our last incident, I don't know why you are here at all, but up to you), you don't seem to get the idea right. See, when you program in whatever language (compiled/non-compiled, old/new, web/desktop, etc.), you are relying on a root directory where all your files are stored. This is the same when you use an online/offline control system/git whatever; the difference is that, in that case, a set of applications manages that root folder and eventually creates backups/secondary folders, and you have to ultimately trust that application + the machine storing those files. I started my programming career as a simulation engineer (emissions in IC engines) and a big part of that work involved to perform lots simulations (= running software usually taking quite long under different input scenarios); there I got used to this approach of replicating folders for running/developing/analysing not just raw data, but also code (some of the simulations required recompiling some parts). I brought that approach to my software development work and have been evolving it since then, such that it is now extremely reliable, secure and hassle-free.

    Logically, I also rely on more standardised approaches/code controls at many different points and for different purposes (e.g., public repositories, projects where I have to use a code control/sharing software, etc.). I don't spend any appreciable amount of time/effort on backuping my code, I have never lost anything of value (that comment about an hour of work was almost a joke) and I am very happy with my current proceeding. In one week of a standard development, I can have around 20 different folders (representing relevant points of that development; note that these are 20 entities that can be managed individually, as opposed to 20 internal differences only recognised by the given control software) in 4-5 different hard-drives, which I can recover and start using almost immediately. You are suggesting me to replace (or plainly criticising it?) that proceeding (which I have been using for over the last 8 years) with a blind trust in a third-party tool (because logically I will not develop a code control software; I did develop all my backup applications though) which will be intrinsically less safe (as commented, just one folder; or perhaps more but managed internally and without me having anything to say there), just because this is what you do (or the only proceeding you can think of?) what makes you think that everyone else should do exactly the same regardless of their conditions, experience, the kind of work they perform and, even much more importantly, what they are feeling like doing? Pfff... Are you seriously still not getting that there is nothing for us to discuss? There are lots of people around, why not trying to talk to someone else?

    --
    Custom Solvers 2.0 = Alvaro Carballo Garcia = varocarbas.
  207. Lol by Anonymous Coward · · Score: 0

    Lol

  208. Idiot by Anonymous Coward · · Score: 0

    The idiot 'developer' himself seems to admit that he clicked the confirmation that files would be reverted, and that he hadn't bothered to commit to source control for three months. Just incompetent. He got what he deserved. I really can't believe that he didn't understand the confirmation dialog wording. His complaint basically seems to be that he wants warning messages for idiots. However, not all developers are idiots, so there would have to be some special version made just for him. Most people will actually be intelligent enough to not need to be treated like they are stupid, and most people would expect the revert option to work exactly like it did - it would be far worse if it did something completely unexpected. I remember back in the days of clearcase, it used to write .keep files for some destructive operations, but source control has come a very long way since the painful clearcase/perforce era, and we don't see any fighting with the scm these days. Even the mention of perforce makes me feel sick - I just hated the branching model in that awful legacy system. Clearcase, at least non-ucm, wasn't as bad, but it died due to slowness and its dated file based commit model, although dynamic views were a neat feature at the time.

  209. Why doesn't he know by meerling · · Score: 1

    The Three Rules Of Computing:
    1 Backup
    2 BACKUP
    3 See rules 1 & 2

    For that matter...
    When did his files become important to him, before or after he lost them?

    A professional programmer that hasn't been backing up his work isn't much of a professional, now is he...

  210. ”Developers” by zynthaxx · · Score: 1

    How is someone even allowed to self-identify as a developer if they lack the understanding - not to mention experience - to perform proper backups of their work? What does that say about the quality of their software? Trainee or junior programmer? Possibly. Developer? Not at all.

  211. Don't even "zip" the files, tar them by Anonymous Coward · · Score: 0

    Uncompressed .tar is nice.
    If you just want to make a copy of a directory full of sub-directories and files, just so that you can be safe if you do something destructive : why waste time compressing it? :)

    I suppose that with hundreds or thousands text files, you save a lot real drive space already - 120 byte files that take 4096 bytes, 4200 byte files that take 8096 bytes - and you're not wasting time polluting the file system with files and directories either.

    I don't know if .zip files support no compression, I once used uncompressed .rar under Windows.
    Uncompressed archive is obviously better for jpeg, music files, small videos as well.

    tar is itself a "data destroyer" command so I recommend just right-clicking the directory in the file manager (I have a "compress..." item in there, then you can select file format including .tar)

    This is incredibly lazy and copies data about as fast it can read it. So why not do something this simple?
    Sure there should be backups and sync acrobatics and version control and Internet, but doing such a very simple "safety" copy even on the same drive (even in your home directory) would be a start.
    This would have saved this guy's work. One right-click and a minute.

  212. git stash bro by Anonymous Coward · · Score: 0

    git stash bro, cmon this is kid stuff

  213. Re:This guy was working 3 month on the same files? by angel'o'sphere · · Score: 1

    So instead of learning how to do it properly you are just developped a habitt that is prone to faillure and an accident waiting to happen?
    And according to your eloquent defense you seem to consider that the superior way?
    A version control system has something called branches. That would make all your individual copies and individuell developed folders superfluvious.
    Good luck in your career, you will need it.

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  214. Hmmm by Anonymous Coward · · Score: 0

    ...backup your files, perhaps?

  215. Re:This guy was working 3 month on the same files? by CustomSolvers2 · · Score: 1

    So instead of learning how

    This is the first and last part which I read from your new likely-to-further-prove-your-extremely-poor-understanding-skills-and-surprisingly-limited-knowledge-about-almost-anything. I will try to never reply to your incoherent nonsense again, here or the next time you decide to arbitrarily and unilaterally start talking to me.

    --
    Custom Solvers 2.0 = Alvaro Carballo Garcia = varocarbas.
  216. Too $hort by Anonymous Coward · · Score: 0

    Cuss words. Let em roll.
    M@$:?!@ S&@/ G@&)"!;$ A$$/)@-

  217. It shouldn't have been 3 hours, let alnoe 3 months by ASM826 · · Score: 1

    You care about it, you back it up. Twice. Automated. Save it on a local RAID array drive. Daily off-site or cloud back-ups so you never lose more than a day. If you didn't back it up, you didn't care about it and it was not important.

  218. Microsoft: The Gift That Keeps On Giving! by I75BJC · · Score: 1

    Hard lesson to learn. Hopefully, it's a lesson that he only needs to learn once.

  219. This is IRREVERSIBLE! by ElizabethGreene · · Score: 1

    Mod parent up for fact-based journalism and actual research.

  220. Just Write it Again! by multi+io · · Score: 1

    There is this "extreme programming" rule that a program should be written twice (starting from scratch both times) because you need the first version to gain a good understanding of the problem domain, which you can then utilize in the second version to actually produce a proper implementation, which will end up being much cleaner than if you had tried to use your deeper understanding of the problem to refactor the first version (in which case the code you're starting from would constrain your thinking too much). So just stop complaining and start over, and you'll end up being glad that you lost the first version. Oh, and in the future, he might still want to use backups and proper version control. :P

  221. moron deletes his own files...? by 2fuf · · Score: 1

    Is this the level you've have sunk to Slashdot? A news article about some idiot clicking "discard all files" when he shouldn't have...? That is news? In 2017?! You think I'm simple or something?

  222. Did this with a Qt pro file and Visual Studio by EmperorOfCanada · · Score: 1

    I changed the files in a .pro file and visual studio simply deleted all the files that I didn't list in the pro file. Not three months, but nearly a day's work just gone. Maybe a heads up when I am deleting multiple files would be nice; and not some ambiguous message, but a clear listing of the files that will be shot.

  223. Paying your dues by ebvwfbw · · Score: 1

    This is called paying your dues. I think all of us delete stuff we didn't mean to. If you're lucky like I was, there's a backup. I've lost some stuff over the decades due to bad hardware, however not much. Stuff I didn't really care about anyway. However I've paid my dues plenty of times.

    Learn from this. Set up your whole life like this. Whatever you do, can bad things happen? Do I need insurance? Do I need better insurance? Can I prevent something bad from happening?

    USB drives are dirt cheap. Buy some. Back up your stuff to them. Switch them out and put it in a safe place. Like a commercial grade safe like I do or even better off site. This time you lost some code. Next time it could be a million in bitcoin or something. Think ahead.

  224. Playing With Prod Files by Anonymous Coward · · Score: 0

    This guys is all at fault for the following reasons.

    1. Why is he "just playing with the source control option" of a new editor using production files. Anytime I start to use a new tool I start by using it for thing that are not that important till I am sure I understand how to use it. And if I do us it for production work I make sure there is a backup of the files I am accessing. You should never "play" with features you don't know using important files that you don't have backed up.

    2. Why was this 3-months worth of work not checked into version control system before he lost the files. I check in code at a minimum nightly for projects I am working on and sometime multiple times per day. If he had his code in a repository it he would not have lost 3 months worth of work.

    3. Even with out using a code repository, he should have at minimum a weekly backup of his files being done (and I would even say nightly).

    I love how people blame MS or any other software maker for stuff, when if standard backup processes and version control is used none of this would happen.

  225. Re:This guy was working 3 month on the same files? by terjeber · · Score: 1

    Actually, you're wrong, he's right. You are also astonishingly ignorant for someone working in tech.

  226. Re:This guy was working 3 month on the same files? by CustomSolvers2 · · Score: 1

    Actually, you're wrong, he's right. You are also astonishingly ignorant for someone working in tech.

    ?! I am wrong on what? On following a proceeding with which I am more comfortable (and using any other one whenever I feel like doing it, because we are talking about using software!!! There is no difficulty on doing such a thing, at least not if you have a bit of knowledge) and defending myself from the random attack (well... not exactly; unless that killing me by sadness might be considered an aggression) of a crazy individual which is apparently obsessed with me (look at all our previous interactions; s/he has always started and always aggressively and always not understanding anything; a quite pathetic spectacle if you ask my opinion). Ignorant of what?! Where have I said anything which denotes my ignorance on any front? Are you even able to understand all the words in the sentence you just wrote?

    I will tell you what I see here: you are either a friend (or part of the groups of fanatics of which s/he is part of) or that same other individual; you are most likely not even a programmer ("working in tech" sounds like the kind of generic meaning-nothing resource that a person with low-to-no actual knowledge but either dishonest or in complete denial uses because of thinking that it seems to indicate that knows what is talking about. Pretty much like that other individual: systematically relying on generic expressions only indicating ignorance rather than knowledge; FYI, I am senior programmer and an engineer) and, just because of this completely-uncalled, pointless and ridiculous comment (which also tells about your ideas regarding fanaticism, arbitrariness and many-against-1 scenarios), I am also sure that you are a true asshole. You are certainly all what is wrong with nowadays software development ("tech workers" as you call them): extremely ignorant fanatics spending all their time attacking everyone for no sensible reason; constantly lying, showing what they don't have, doubting on anything, not having even basic knowledge (but probably getting lots of money on exchange of shitty software, what seems a bubble which will most likely explode at some point). Your kind is the reason why I don't want to contribute/participate in online programming forums at all. Now, please, go with that other half person somewhere else to say these abstract sentences to the only audience which tolerates them (other ignorant idiots like you), to continue thinking that you have any kind of opinion/authority (and that you saying "it is like this" has any meaning at all) and don't bother me with your pathetic nonsense anymore.

    --
    Custom Solvers 2.0 = Alvaro Carballo Garcia = varocarbas.
  227. Re:This guy was working 3 month on the same files? by williamyf · · Score: 1

    Niños por favor, vayan a jugar a otro lado, los adultos queremos hablar.
    Children please, go play somewhere else. The adults want to talk.

    It seems you guys have a "Cable pela'o" of some sort, that somehow ended up as a reply to my post. And with no context to boot. If I had context, I might try to mediate, but, being things as they are, I guess you guys should exchange contact info, do a skype/webex/webRTC/whatever conference call, and sort it out...

    Fichez nous la paix.

    --
    *** Suerte a todos y Feliz dia!
  228. Re:This guy was working 3 month on the same files? by CustomSolvers2 · · Score: 1

    Niños por favor, vayan a jugar a otro lado, los adultos queremos hablar.

    Pretty good Spanish for whom I presume that isn't a native speaker.

    It seems you guys have a "Cable pela'o" of some sort,

    I am not getting this one though. I understand that it is slang in some Spanish-speaking country different than Spain (but "pelao", as short-form of "pelado", seems better than "pela'o"). I presume that it means that we are acting crazily or something like that. There is certainly something wrong with these other people (at least, with their understanding capabilities and expectations), but I plainly wrote a pretty soft and completely on-topic post which got the kind-of-attack of an individual who seems to have some problems with me (and, most likely, in general too) and, since then, am plainly replying to increasingly stupid comments. I have never been even slightly angry (not even disappointed with that guy/gal, as far as I know him/her from previous threads); I am plainly being extremely clear regarding the kind of invasive, stupid, fanatic, ignorant nonsense/people with whom I don't want to deal.

    that somehow ended up as a reply to my post

    No idea what you are talking about. I have been here all the time replying to the (self-invited) answerers (mostly with an unmotivatedly aggressive attitude) to my original post. This whole "problem" started because I shared my approach to deal with code versioning/backups, that weird/crazy/obsessed-with-me individual decided that my approach wasn't good and, despite having had a quite hard discussion in the past which any sensible person should have understood as "there is nothing to talk with that guy, let's better deal with other people", brought their limited understanding capabilities here and seriously believed that, regardless of my experience, having always got excellent results (= no hassle, no effort, no problems) and, most important, wanting to use said proceeding, thought that could "convince me" (= being angry if I didn't do what s/he was saying me to do) to use a different approach. All this by bearing in mind that we are talking about something as simple and non-problematic, as plainly using software!! And that I am quite flexible on what to use regarding the conditions. It has been something like you mostly using editor A (+ sometimes other ones) and a (self-invited) person comes to you and says that you have to use editor B, that nothing else is acceptable!?

    And with no context to boot.

    There you have your context, but please don't take this as an invitation to extend more something which I consider completely and absolutely stupid since the first moment. I guess that that individual (who clearly have some issues with me or in general, I don’t really care) have written comments somewhere else. No idea what s/he said and I don't care. For me, that person is completely crazy in the sense that I don't want to deal with him/her, but continues coming to me with their nonsensical expectations (and my reactions are likely to keep getting increasingly more aggressive).

    I might try to mediate

    I am a sensible, reasonable (and even cold, if you wish) enough person to not need any kind of mediation when dealing with any other person. By assuming that there are two types of people, the ones with whom it is possible to talk and the ones with whom this isn't an option; I plainly don’t want to deal with the second type. Currently, I am being extremely clear regarding my position with respect to that second type. To speed up the understanding process (some people have serious problems to understand concepts like this; no idea why! Surprisingly, they usually have extremely unappealing behaviours, but they are convinced that anyone else have to like them?!), I have no problem in being as (even hurtfully) clear as required. If you want to help someone, talk to that person and make

    --
    Custom Solvers 2.0 = Alvaro Carballo Garcia = varocarbas.
  229. Re:This guy was working 3 month on the same files? by williamyf · · Score: 1

    Hijo mio, soy Venezolano.

    Si eres español, mis condolencias por lo de Barcelona.

    Revisa "Cable pela'o" (o pelao, como prefieras) en el diccionario de Americanismos de la asociacion de las academias de la lengua española.

    Pero en fin... considerando que mi posteo es el "abuelo", y que todo el vacilon de ustedes dos esta debajo del mio, y que, como uno de ustedes dos dijo, ustedes se conocen "de atras", pense en decirles...

    Pero en fin. Ustedes ya son mayorcitos, y sabran que hacer...

    En español de españa: a mi me la suda...

    Mucha salud y felicidad a ambos...

    --
    *** Suerte a todos y Feliz dia!
  230. Re:This guy was working 3 month on the same files? by CustomSolvers2 · · Score: 1

    Hijo mio, soy Venezolano.

    Vale, papi, lo de "william" me despistó (pero supongo que yo tampoco puedo hablar mucho en ese frente). LOL.

    Si eres español, mis condolencias por lo de Barcelona.

    Gracias. Cómo repagar ese gesto a un venezolano? Sé que algo había pero no caigo yo ahora... LOL

    En español de españa: a mi me la suda...

    Ahí estamos! Hablando con claridad!

    Encantado y a más ver.

    --
    Custom Solvers 2.0 = Alvaro Carballo Garcia = varocarbas.
  231. Doxxing is noble now? by Anonymous Coward · · Score: 0

    Doxxing is noble now?

    1. Re:Doxxing is noble now? by Lord+Kano · · Score: 1

      I googled the user name in the article.

      It's not doxxing to find publicly available information.

      LK

      --
      "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
  232. dialog by Anonymous Coward · · Score: 0

    You mean you clicked the option that generates the dialog: "Are you sure you want to discard ALL changes? This is IRREVERSIBLE!" and then clicked the button "Discard ALL Changes"?