Code Copying Survey for Developers

Struan Robertson writes "With all the controversy surrounding SCO's allegations that its Unix code was copied into Linux, we're running a survey with ZD Net to gauge industry practice on code copying. Do you keep a code library? Do you take it from one employer to another? These are the questions we're asking. All answers will be anonymous. The results - with expert legal analysis - will be published free - we're not doing this to sell reports etc. If you're a developer and happy to help, see our questions on SurveyMonkey.com."

Loop

[andy666]

I think the first person to write a loop should complain a lot!

Yup, and I keep it...

[tcopeland]

...right here [rubyforge.org]. And here [sf.net], too.

And lots of other folks contribute too. Good times!

Do you keep a code library?

[Anonymous Coward]

Hell no, I like rewriting conversion and formatting routines. That's like a paid vacation!

Re:well..

[Anonymous Coward]

You mean the part about getting paid to write code?

Re:Sure, Why Not?

[Throtex]

And when that happens, I wanna be in that platoon!

I get paid hourly

[BillFarber]

Why would I keep a library of code to help me get the job done faster and for less money?

Re:Loop

[RLW]

Hey, I was the first to write an infinite loop. I should get infinitely more money than loop-boy!

Re:Do you keep a code library?

[RLW]

Exactly. Why keep a code library around when you can get paid to rewrite stuff which can be put together nearly in your sleep? It's a good way to start the day while I'm still groggy. Then I can get paid to debug it in the afternoon after I wake up.

Re:Good memories are for wimps

[Anonymous Coward]

My memory sucks - as is true of all good C++ coders

Exactly how do you figure that. I happen to have an excellent... wait what were you talking about?

Re:Sure, Why Not?

[Sbev]

Code samples are a joke... Who knows who really wrote the code.

The point was driven into me when I was hiring several contractors for some positions. Standard company policy required developers to submit code samples. One day when I was reviewing candidates, I noticed a previous employee's name in the list. After I checked the code samples I almost fell on the floor.

First he sent code that was written while he was working for the company, in direct violation of his signed severence agreement. The company's copyright was in the header of the first file I opened.

Second, the code looked very familar. Reviewing the code closer, I realized I was actual developer who wrote the code. The code was for a project that he was never allowed to touch.

In short... please don't go by code samples...