SQLServerCentral Editorial

A Paste Policy

,

Most of the code I've written for various employers was something that lived inside the organization. This was for internal use and no one outside of the organization ever used it. It was almost always code I'd written, so I wasn't ever worried about the provenance of the code (where it came from).

However, I'm sure I've copied code from somewhere online and used that in some way. I might have taken this function from Jeff Moden and dropped it on a production server where it was used to process a string. I'm sure I've taken code from various places and used it in administrative functions, like Ginger's code to manage a log file.

I don't know that any of those authors would have minded using their code. After all, that's why many of us have written articles and published things at SQL Server Central. We are looking to help others grow their knowledge, as well as provide them short solutions they can incorporate into their own work. I assume most of the people answering questions at SQL Server Central or Stack Overflow feel the same way. Use the code.

In this new age of AI, perhaps that's OK, or perhaps it's not. There is concern about who owns code and who has rights. At Redgate, we build software that's sold and installed on other machines, so we have stricter guidelines. Our policy (in general) is "You MUST NOT include source code of unknown provenance in your application." I saw a note recently that said this also applies to any AI-generated code, even if we provide the prompts.

I doubt many organizations have policies about using code from the Internet, but I wonder if they should. Possibly there might be ownership or usage issues with AI code. If someone posts code on SSC that's one thing, but getting code from an AI that might have been trained (and regurgitates) code that is not freely posted could be a problem.

Maybe it doesn't matter. After all, in your corporate CRUD application or some DBA maintenance script, it's unlikely anyone will be auditing the code for any sort of misuse or copyright infringement.

Rate

5 (1)

You rated this post out of 5. Change rating

Share

Share

Rate

5 (1)

You rated this post out of 5. Change rating