IDE ate my source code
A tale to chill the blood of developers everywhere: "My IDE ate my source code" [For non-developers, "IDE" means "Interactive Development Environment", and is how developers like to edit source code.]
My attention was drawn to the line "I've been using Borland IDEs on and off for the past 17 years or so, and nothing like that has ever happened before."
Quite frankly, I gave up using Borland IDEs oh, a little over ten years ago, because the IDE I was using did exactly that - ate my source code.
I'd typed in a bunch of new code, and wanted to test it, so I pressed the button to debug my code. Of course, the code crashed, and this being 1995, and on Windows 3.1x, it took the operating system with it.
After I rebooted, it became clear that my last several hours' worth of work had not been saved. Say whuh?
The Borland IDE of the time would happily compile code without first saving it. [My first thought was "how can it even do that? The compiler works from source files on the disk, surely?", but I confirmed that you could create and compile an entire application without it ever hitting the disk except as object and executable code!]
[How is this security related? Let's say you fix a security flaw, and make a bug fix elsewhere. You test the code - the security flaw fix works, the bug fix crashes when you test it. So you reboot, and go make the bug fix in a different place, thinking your security fix is still in place...]