One day on the Internet when I was searching for SharePoint best practices I found a google cached site called SharePoint Worst Practices. I thought it was hilarious and represented not only things I have seen in real life, but the challenges with doing things the right way instead of the easy way. Behold, SharePoint worst practices:

​·         TSQL UPDATE queries against Config DB on a production system during production hours

·         TSQL DELETES … why?    because we can!     worry not friends “STSADM databaserepair” will clean up our leftovers

·         TSQL craziness including XML blobs and decoding GUID relationships

·         Using ROBOCOPY to subvert change management processes

·         Using scripts to cause massive outages … faster and bigger than you could do alone!

·         Fun with CORE.JS and global pop-up dialogues

·         Removing system features by deleting some stuff in \12\ hive

·         HOSTS file instead of DNS … because everybody loves notepad!

·         RDP-ing as system account.     who can remember all those funky symbols in passwords anyways?

·         Go crawl yourself!     boosting asset utilization while crushing performance with INDEX machine loopbacks​

If the real author finds this and steps forward, I would love to given attribution. Happy SharePointing!