The horror story that I heard was a disgruntled engineer silently replaced the source codes (C++ based) in the project with compiled binary object files and he kept the source codes on his local computer, not checking those in. He did this over an extended period of time to make sure this crept into the backup tapes as well. No one found out because each engineer owned a code module of their own. Then he resigned. Wh…
My god, i'm surprised that person didn't land up in court :/
Things to commit just before leaving your job
91–100 of 165 posts
Re: Things to commit just before leaving your job
#92Earlier quoted context omitted.
I am curious - wouldn't your Version Control system catch this and warn him that "file xyz has changed since you last checked it out, ..." etc?
There is no warning. Pull cp * ../work cd ../work Work (cd ../src && pull) cp * ../src cd ../src Commit
Re: Things to commit just before leaving your job
#93Re: Things to commit just before leaving your job
#94Something I wrote to amuse the junior front end developers here: document.write('Error: Script not found.'); var node = document.currentScript; if (node.parentNode) { node.parentNode.removeChild(node); } Pop that in a JS file called something like jQuery.min.js and add it to an HTML page with the usual . It'll run when the page loads, add the line of text to the page, and then it'll remove it's own tag so there's no…
Re: Things to commit just before leaving your job
#95Re: Things to commit just before leaving your job
#96Earlier quoted context omitted.
My god, i'm surprised that person didn't land up in court :/
Is that illegal though? Sure, if you can PROVE it is done on purpose then maybe, but assuming you cannot then is it? Because if it is then any misconfigured version control or any employee that doesn't do what is expected of them is also breaking the law.
As an employee of a company that provides you a paycheck, you "owe" them your best effort. If you don't want to try, quit - but don't sabotage. That is juvenile and perhaps illegal and certainly unethical.
Re: Things to commit just before leaving your job
#97Ooh. I recognize one of the contributor names, @cmuratori, from another HN post: Handmade Hero: C game from scratch https://news.ycombinator.com/item?id=8604489
Re: Things to commit just before leaving your job
#98I would suggest before you leave your job, you say "it was nice working with you" to the people you liked working with, and absolutely nothing to those who you did not enjoy working with. The tech world is big in some ways, but also equally small in others. A select few might find this funny, but others will not appreciate their day (or longer) spent debugging your practical joke...and on the chance you actually get…
And if you do a code change, make sure it is really funny, is easy to fix and discover and is invisible to customers. Like, inject a hilarious joke into the log files or something.
Kinda funny, no customer impact. Not sure what would have happened if he had a bug and made ghosts appear for everyone...
Re: Things to commit just before leaving your job
#99Oh I so desperately need a PHP equivalent right now.
PHP actually allows much less mischief here than C or, say, Python does. It doesn't let you redefine or delete functions, classes or constants, unlike C where macros can be abused for this, and Python where you can delete anything. But you could hide all errors if you want to screw with people: error_reporting(0); set_ini('display_errors', '0'); set_error_handler(function () { return TRUE; }, E_ALL | E_STRICT); set_e…
Re: Things to commit just before leaving your job
#100We've got a guy in the office that merges the past over the present all the time. He's not quitting but I imagine if you were to try to break things this would be a good way to do it.