3 ms·
My biggest problem with coding for an employer, is that they then own exclusive rights to the code. Essentially, you are solving a problem. If that problem is
by derekp7 11y ago
My biggest problem with coding for an employer, is that they then own exclusive rights to the code. Essentially, you are solving a problem. If that problem is unique to the employer, then that is fine for them to own the code. But if the project involves writing a bunch of potentially reusable routines, such as what you might find in a third party library, it just seems awful that you can never solve those same problems again in the future (as more likely than not, you will end up typing in about the same code).
So it really seems like you are giving up a piece of your mind whenever you program for someone else. For an example of what I'm talking about, see XKCD 664.
- dudul 11y agoWell, it's not like they pay you to write code for them right? It is only fair that your are, in theory, not allowed to reuse the code who wrote for them at your next gig. And to be clear, we all do it. If you've implemented it once you can redo it in no time.
- derekp7 11y agoI agree that it is fair, it just kind of hurts a bit is all. Especially if you did something you are real proud of. I wish there were more programming jobs that were similar to photography -- you get hired to do a shoot, the customer gets a copy, but you keep the copyrights.