Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 155 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Possible Duplicate:
I’m worried about Stack Overflow content licensing

This question came up today at work and I thought I'd (ironically) ask SO about it - have other employees at your job voiced legal concerns about reading responses to your SO questions, with the intention of incorporating the knowledge into production code?

For example, if a user posts code to do something and you copy-paste it into your app, what does that mean to your app? While all of our answers are CC-licensed, CC-Wiki doesn't really fit code. Does your company worry that someone will accidentally let out semi-internal information about $PRODUCT in an answer?

share|improve this question

marked as duplicate by Kyle Cronin Jul 28 '09 at 2:23

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

Feel free to read here… on the implications and resolutions. – Ian Elliott Jul 28 '09 at 2:17
I don't think this is an exact duplicate - while code is a major issue, there are other legality issues with SO; I wanted to discuss the broader issue :) – Paul Betts Jul 28 '09 at 2:46

Well unless your post goes something like "Hi, I work for Apple and we're releasing this X in 3 months and I need to make sure features Y and Z work with Cocoa" I wouldn't really worry about the bit about releasing information you shouldn't.

More to the point, I think you'll find that people rarely (if ever) copy and paste code directly from something commercial. For one thing, it's rarely appropriate. There'll be a lot of stuff in there that's just not relevant to the question. A good question will have reduced such code to a small test case, in which case it no longer resembles the original code.

Likewise the answer will be for the simplified problem, not for your code, so copying and pasting it verbatim is (imho) unlikely.

The value in SO answers is in helping you understand the problem and finding a solution. You then apply that solution to a similar (but ultimately different) problem at work.

Now if that solution has a problem in it, you have two safeguards. Firstly, it will hopefully get downvoted. That doesn't always happen but it usually does. I've seen bad answers get upvoted. The second is that you are ultimately responsible for any code you produce at work. So you can use something you found on the net but by putting it in you are using your professional expertise to vouch for its efficacy, robustness and appropriateness.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged .