network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years, 9 months |
| seen | Mar 8 at 21:55 | |
| stats | profile views | 40 |
|
Feb 26 |
awarded | Constituent |
|
Feb 19 |
awarded | Caucus |
|
Sep 24 |
awarded | Yearling |
|
Aug 16 |
awarded | Nice Answer |
|
Jun 28 |
comment |
Should you keep a copy of all the code you write? @DexterHuinda My wife doesn't like my code collection either... :( |
|
Jun 27 |
awarded | Great Answer |
|
Jun 26 |
comment |
Should you keep a copy of all the code you write? Apart from not agreeing with your comparison there (500 hrs down to 20 hrs is wishful thinking), but you also fail to consider what the employee might have brought into his job that this employer would benefit from. It cuts both ways. |
|
Jun 26 |
revised |
Should you keep a copy of all the code you write? Remove the question at the end. |
|
Jun 26 |
comment |
Should you keep a copy of all the code you write? The second item assumes that there would be an open source solution, which is far from certain. But most importantly, some of the code I've retained is code that demonstrates how I've used 3rd party components/services. For example, if I develop a decent payment solution that integrates with Paypal, I'll take the code to refer to later - so I don't need to re-invent the wheel next time. |
|
Jun 26 |
revised |
Should you keep a copy of all the code you write? deleted 197 characters in body |
|
Jun 26 |
awarded | Citizen Patrol |
|
Jun 25 |
awarded | Guru |
|
Jun 25 |
comment |
Should you keep a copy of all the code you write? @Krelp - why are you quoting US law? A fair proportion of us do not live in the US. I appreciate your sentiments, but this is an international forum, and you need to be mindful that some parts of the world do things differently. |
|
Jun 25 |
comment |
Should you keep a copy of all the code you write? @Malfist - in my jurisdiction, if you develop the code in company time, or as a consequence of your employment, the company own the IP. Likewise, the 3 elements that I developed in my own time, for my own purposes, that my current employer uses, is entirely my property. I advocate taking selective copies of your code (for reference), but it's important to be aware of the legal implications in your jurisdiction. |
|
Jun 25 |
comment |
Should you keep a copy of all the code you write? @Caleb - my previous employer gave me the CDs to write the code to. And no they didn't try to tap me for technical support. I almost certainly took code that someone else contributed in some way to... As for the legal angle, I think some people are a little confused. In my jurisdiction, the company owns the intellectual property and the right to use the code - they don't own every printout or binary. |
|
Jun 25 |
comment |
Should you keep a copy of all the code you write? I've just discussed this with my wife; she works in a completely unrelated sector, but she agrees that this happens in her sector - and everywhere else too. You don't take binaries to your next job, you don't even copy-paste source code... but you do cherry-pick the best bits for future reference. And I do think too many people 'doth protest too much'... |
|
Jun 25 |
awarded | Good Answer |
|
Jun 25 |
awarded | Mortarboard |
|
Jun 25 |
awarded | Nice Answer |
|
Jun 25 |
answered | Should you keep a copy of all the code you write? |
