Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Things to commit just before leaving your job

gist.github.com

Post reply on HN
Print view View original

31–40 of 165 posts

Re: Things to commit just before leaving your job

#31

Post by DeusExMachina »

It is always a funny joke to say "commit this when you leave a job". But I always wondered if there are people that actually do this.

Although it could be funny and give a sense of revenge for some wrong (perceived or real) that the person leaving might have suffered, I don't think this would be a good idea. Contracts usually include liability for gross negligence or wilful misconduct.

Does anybody have a record of this actually happening at any company?

Re: Things to commit just before leaving your job

#34

Post by jerven »

praseodym wrote: post #19
mavelikara wrote: post #10

Earlier 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?

DVCS systems like Git and Mercurial will require you to merge, but if you use a GUI VCS frontend it's really easy to choose the "use my local stuff" button. Been there with some university projects groups. (These people also liked the "force push" method of merging.)

You turn this capability off. I did and I sleep much better since!

Re: Things to commit just before leaving your job

#35

Post by odonnellryan »

hellofunk wrote: post #15

Perhaps the most enlightening (and actually useful) purpose of this file is to dramatize the glaring weakness in the c/c++ macro system. A proper macro system would not make it so easy to do this, shall we say, "evil", stuff :)

You can do some gross stuff in Python, as well!

Re: Things to commit just before leaving your job

#37

Post by onion2k »

Something 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 reference to it in the DOM (in relatively modern browsers) if you view the source. It's easy to debug by watching the network traffic, but it caused a few scratched heads for a little while.

Re: Things to commit just before leaving your job

#38

Post by joncp »

DeusExMachina wrote: post #31

It is always a funny joke to say "commit this when you leave a job". But I always wondered if there are people that actually do this. Although it could be funny and give a sense of revenge for some wrong (perceived or real) that the person leaving might have suffered, I don't think this would be a good idea. Contracts usually include liability for gross negligence or wilful misconduct. Does anybody have a record of t…

Worse. Depending on the jurisdiction, they may be able to get you arrested for hacking.

Re: Things to commit just before leaving your job

#40

Post by cjrp »

wil421 wrote: post #6
yarper wrote: post #2

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

Got a offshore guy just like that. Constantly committing his whole project where most files are out of date and only the few he worked on are not. There's no reason for him to commit javascript files he doesn't even work on the front end. It took me forever to figure out he wrote over my files the other day.

He must be using push --force in that case.. which seems like a bad practise.
Post reply on HN