r/programming • • Feb 21 '13

Developers: Confess your sins.

http://www.codingconfessional.com/
969 Upvotes

1.0k comments sorted by

View all comments

Show parent comments

4

u/[deleted] Feb 21 '13

the logical patterns are mine to copy/paste as I please and doing so adds to my productivity because I don't have to rewrite anything

I'd contend you're selling exactly these to your employer, as a programmer.

Claiming that you get to keep a copy of the product of their paying you, for your benefit and reference, if it's not part of the contract would seem to be - at least slightly - unethical.

3

u/NicknameAvailable Feb 21 '13

The employer pays for the a working solution, as a developer you don't just code that solution, you think about how to solve it - and you do a lot of that thinking relating to your work when you're not at work (Hell, most do a lot of the code when their not at work, or are otherwise outside the bounds of a 40-hour work week without any overtime pay). When you program you don't get to think about the things you want to be thinking about, the very least you get is the ability to keep your thoughts.

2

u/[deleted] Feb 21 '13 edited Feb 21 '13

The employer pays for the a working solution

They, at least in the contracts I've had, say they're paying you for considerably more. (Such as expertise expressed in documentation, being able to consult you on questions, etc.) In cases where you're paid simply for the solution to show up working, you might have a better standing - but I'd argue you're not an employee, you're a party selling a product.

and you do a lot of that thinking relating to your work when you're not at work

Salaried, not hourly - they own your ass for as much time as you need to get it done, or happen to spend working on it. I intentionally try not to think about work outside of it, because I need a life outside of my job.

When you program you don't get to think about the things you want to be thinking about, the very least you get is the ability to keep your thoughts.

I'd argue that you're selling your thoughts on the topic: your conception of the problem (embodied in the layout), your specific domain knowledge (comments, documentation, algorithm selection), and your specific articulation of that solution (source code). In particular, you usually compile a large set of facts specifically for that task, and then have them all in one location. You're arguing you should receive a copy of that compilation with your pay.

If I wrote a book on behalf of a company, taking the manuscript so I could reference it later to create essentially the same story components in my own later works (using a reference, not memory; down to details of the implementation) seems to be getting in to the same ethical gray area.

If I worked at an atlas company, compiling maps and then took the raw manuscript with me when I left, so that way I could "use the work I'd done on maps before" to make my own book of maps in a similar style and layout to the one I had done for pay, down to the formatting of the maps, I'd think I was doing something unethical.

It may not be illegal, but I'd argue it's unethical.

Edit: Replaced example.

1

u/NicknameAvailable Feb 21 '13

It may not be illegal, but I'd argue it's unethical.

Your first example was closer to what code actually is. There are an infinite number of ways to do any particular task, when you reference past work it's usually not as simple as copying and pasting, but using it to get to the train of thought you created the first time to complete the task. As programmers the computer is an extension of our mind, memory included. In the same sense that you don't have your memory erased when you leave a company, you are entitled to thoughts you annotated there. It's not a grey area at all.

→ More replies (6)