While I usually agree with comments like these, I think it is key to point out that respect is earned, and that just because some code has been released it does

While I usually agree with comments like these, I think it is key to point out that respect is earned, and that just because some code has been released it doesn't mean that we should be grateful for it being bestowed upon us. Nowadays, when I release any code I tend to write a description of said code to illustrate how I intend it to be used. If I'm writing something that I believe shouldn't be used on a production project I will explicitly state this. I don't release a lot of code, but I've released a few snippets of untested, hacky code before that has found its way into production sites, and the last thing I want is for people to slate me just because I thought I'd show off what I had written. This kind of thing happens all the time, almost monthly on Hacker News and Reddit. Everyone would probably be a lot happier if people were to add a basic disclaimer to their code to say "Hey, I've written this for a bit of fun. Don't use it on a user-facing site, okay?" to released code if they don't intend for it to be used on production sites by others. It may not be applicable in this case, but I reckon most cases where people bitch about how shitty some open source code or technique is would be solved if an author would explicitly state the use case for their code.