Skip to content

Comment on Is it ethical to keep a copy of the code or designs you did for your employer, for your reference?parent

Comments

Interesting...at the places I've worked (as an employee), it was considered a dealbreaker if a contractor wanted to own the source code they produced. We passed up some really, really good contractors because they wanted to own the product.

juwoOP

please also comment on A) since the person is likely to become an investor in my product in the near term.

I'm not actually commenting on either A) or B), just on menloparkbum's comment that it's common for contractors to retain ownership.

I don't really want to get into the ethics of it, because I don't think ethical debates are particularly fruitful. (I took a course in meta-ethics in college, which makes me particularly suspicious in attempts to ground ethical judgments in factual statements or logical debate.) I'll tell you that I wouldn't do it; it sounds dodgy enough that I wouldn't really want to get involved with it. Ultimately, most ethical judgments come down to gut feelings about right or wrong.

I will say that right or wrong, I think it's stupid. You're opening yourself up to big legal liability. If acquirers or investors find out about it (and they will - that's what due diligence is for), they will nix the deal. Heck, I'm spending about $1K to have a lawyer draw up a release to make sure all IP I developed for my startup while employed belongs to me, and I didn't take any source code from my employer (I'm using a completely different technology platform and am in a completely different area of business.) It's just something I don't want to fuck around with.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.