Live data from Hacker News

Things to commit just before leaving your job

gist.github.com

161–165 of 165 posts

Re: Things to commit just before leaving your job

#161

Earlier quoted context omitted.

what happened as a result? im curious to know.

The CEO decided to just move on because it was a small company with less than 30 people. Litigation would take too much time and money. The engineering team took a couple of months to figure out what that module did and rewrote from scratch.

thanks for replying. i can see where the cost would outweigh just re-writing.

Re: Things to commit just before leaving your job

#162

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

Seems pretty straightforward to me: the intellectual property of the code this employee was developing lies with the company (per default).

Either he still has the code, in which case he's supposed to hand it over.

Or he deliberately destroyed it, which means destruction of company property. Deliberate? Yes, because a programmer claiming "oh didn't realize you wanted to keep the source codes!" is not going to fly very far in court.

(BTW I'm modelling this on my assumptions about how this would play in Dutch court, which can be delightfully pragmatic. So there might be some differences how this would work in the USA, such as others commented, ability to afford justice in the first place)

Re: Things to commit just before leaving your job

#163

Earlier quoted context omitted.

Is it worth the risk to find out? Court ain't cheap, even if you win. 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.

> you "owe" them your best effort Yeah, and the company "owes" you as high a salary as they can possibly afford...

> Yeah, and the company "owes" you as high a salary as they can possibly afford...

When a company makes a job offer, you agree on the salary. For X dollars, you agree to be their employee and do your job. Your job is not to sabotage a project or commit binaries where people should commit source code...

Pretty sure if you had employees you would not love it if they did that.

Re: Things to commit just before leaving your job

#164

Earlier quoted context omitted.

A friend of mine did something similar, not that long ago. His employer told him to complete a 1-year masters in computing at his expense, including a course on ethics, or see them in court. He chose the degree course.

That's almost benevolent on the part of the employer -- having more degrees can only be good for the person's employability, and it was most likely an enriching experience to boot. Oh well, i guess some people have larger hearts than i do! :)

I suspect my friend had friends in high places, or else the employer (a well-known name) was looking to avoid public embarrassment.
Post reply on HN