SQL writers, bloggers are not citing their sources

One thing I’ve noticed recently, over the last year or so, is the increasing problem in our large SQL Server community of writers not citing their sources of information as they should be doing.  I include folks over at SQLBlog.com, SQLServerPedia, personal blogs, SQLServerCentral.com, SQL Server Magazine, etc…really, most everywhere, I’ve noticed a wealth of information and technical explanation with no reference as to where the information came from, who wrote the original material, or where the idea was sourced. Amazing! There is no way, absolutely no way, for instance, that a writer could recite by memory the entire release schedule, including dates, for Microsoft SQL Server over the past five-seven years.  I just saw this blog today; I also happened to scroll to the end with no reference to anything or anyone.  This is shear brilliance I tell you!

Or, maybe it’s someone who does not have the inclination or smarts to take a step back and give reference to his or her material, which is the right thing to do. I found a handy guide(1) to look at when writing in a quick search. Go search for one that you like. This one includes an explanation of references, when to cite the notion of common knowledge, and plagiarism among other things. Here is an excerpt of when to cite sources:

1. Direct quotes of more than one word. If the author’s words are powerful or you need to be specific for your argument, the authors’ words can be used as a direct quote.
2. Paraphrasing or summarizing. If you want to use someone else’s idea to help you make your point or to support your own ideas, in this case you would “translate” the ideas into your own words.
3. Information which may be common knowledge but still unfamiliar to your reader. This would also include statistical information which may be familiar information but still requires confirmation.
4. Not just books or articles should be cited. Any source that you use for information can and should be cited including interviews, websites, TV programs, etc.
5. Whenever you are not sure if something should be cited, err on the side of caution and cite sources.

Note that in bullet item two…this includes paraphrasing or summarizing. In other words, if you take an idea from someone and blend it into your blog or writing, but change it up so that it may very well not even be recognizable from the original work, you should still source the material. As I mentioned in another post a few years ago on this site…if it’s not your work, it’s not your work. (That blog was solely on plagiarism, downright copying word-for-word another person’s work). Number five also jumps out – if you are not sure, then you should cite the source.

I learned when going for my Master’s degree the professional and courteous gesture of citing another’s work. You also were required to practice this, or be subject to a letter grade ‘F’ and/or expulsion from school. While not everyone in the SQL or even dev community has an advanced degree, or even a degree at all, they’re not excluded. And, you don’t need to go get the latest APA book to get the correct format for a citation (no one is going to grade you) either. Just a simple “Hey I got this info over here from this dude” will suffice. Even if it’s Books Online. Yes Books Online.

I’m not perfect in this area either – note that the title of this writing does not include an “except for me” caveat. But if you go look at a lot of my blogs and you’ll find references where required, and more often than not.  If I fail to cite someone, I normally have a link to their original work. And, yes, sometimes I just flat-out forget, so we all need work in this area. However, what I’m seeing is an incredible amount of copied or sourced information where no credit is given.  You’re MCM isn’t all that, and neither is your MVP... neither accord to you a favored status to be exempt from the courtesy and professionalism of citing someone’s work. And if you just so happened to have written part of the SQL Engine, well, you’re not excluded either, because you didn’t write the entire SQL Engine.

Your work can describe you as a professional database writer, technician, and practitioner, or some random hack. So which one will it be for you? Think about it.

Lee Everest

------------------------

References

(1) Univ of Albany. When and Why to Cite Sources. Retrieved 2/17/12 from
http://library.albany.edu/usered/cite/citing.html