SharePoint is a woman-Absolutely!!!

SharePoint is a woman

Yes.. I’ve said it before and I’ll say it again. SharePoint is all woman. Here is why:

“If you don’t know why I’m mad, I’m not going to tell you!”

Other reasons SharePoint is a woman:

• You can either fight SharePoint to make her do what you want, or you can let SharePoint do what she wants to do and learn to work within those constraints.
• If you don’t let SharePoint eventually do what she WANTS to do, you will be miserable.
• To truly appreciate SharePoint you have to invest a lot of time getting to really know her.
• Gifts (ie more RAM, more servers, etc…) are always appreciated and keep her happy for a while.

The right way to do most things in SharePoint is… “It depends”

There are definitely some best practices out there, but a good 80% of the time the right way to do something will depend on a plethora of circumstances for a given situation. There is no boiler plate recipe for deploying sites that will work every time. It will not always make sense to use the same development tools every time. Every situation has to be examined to identify its best practice. The ability to know what is best for a given situation can ONLY come from experience. You won’t learn this one in a book or class.

Just because you got it working, doesn’t mean you got it working right.

This one goes hand-in-hand with the previous quote as well as the next one. Just because you figured out a way to get some functionality to work, it’s not necessarily a good idea. Did you remember to dispose all of the correct objects? Did you have to manually copy anything into the 12 hive? Can you maintain it? Will your admin kill you for doing it? I’m never quick to pat myself on the back when I get my desired functionality working. I try to always bounce ideas off of those thousands of people smarter than me and do a quick search to see how others solved the same problem. Twitter is invaluable for this.

You WILL run into performance issues.

So, yeah… there are a billion and a half gotchas that can or will cause performance issues at some point. Bad code, bad Infrastructure, bad taxonomy, bad users, even abuse of versioning in document libraries can all contribute to performance problems and wow, so can so many other things. Luckily there are some brilliant people out there who are experts in SharePoint performance, and for a nominal fee they’re more than happy to lend to a hand. One thing is certain, a user will utter the phrase “It’s so slow!” at some point.

Some people will NEVER “get” SharePoint

Most end users can, with time and effort, be trained on what SharePoint can do for them and how it can make their life easier. When someone has that SharePoint “Aha!” moment and embraces it, that’s when things really start to click and make our lives easier.  Some people, however, will never get SharePoint. They are either so biased that they will never give it a chance, resistant to change and can’t get past the differences, or have to have their hand held to do anything. These people are the bane of all those who have sipped from the SharePoint Koolaid. Some people are always going to want to email attachments, gripe because SharePoint is not what they are used to, complain because it “looks like SharePoint”, or want definite yes and no answers that apply to every development scenario. Worse yet are those people who don’t get SharePoint but THINK they do! “Wow.. I have a great idea! Let’s upload an excel spreadsheet to a document library and we can store our vacation schedule in it so everyone can check it out and edit it in one place!!” At some point it hit me that some people will never “get it”. On the bright site, that can mean more job security???

Content taken from Mark Rackley’s blog http://geekswithblogs.net/SoYouKnow/archive/2010/01/13/sharepoint-pearls.aspx

Special Thanks to Mark Rackley