4 ms·
I have a question related to this. Even though my primary role isn't development (I'm systems engineering), there is some programming work involved. If I pour
by derekp7 12y ago
I have a question related to this. Even though my primary role isn't development (I'm systems engineering), there is some programming work involved. If I pour a lot of effort into something good (say a tool kit that makes future code easier), it is very hard for me accept that the code is owned by the company I work for, and I can't use it on any future jobs. Kind of makes me want to do a so-so job, and save the good code for my personal projects. How do professional developers deal with this internal conflict, other than no caring about the code you write for work?
- arebop 12y agoHere's what I do: Work at a company that encourages/allows you to do free software development. Then you only have to write proprietary code that's not generally-useful anyway; no conflicts!