That O365 Guru from Cape Town (#NadirKamdar)

When we look at the minimum resources needed for a SharePoint environment, we think SharePoint administrator and maybe the “can-do-it-all” SharePoint Developer.    Don’t get me wrong, these resources are great and are vital for the stability and growth of the SharePoint environment, but they are essentially the workers, or the term I like using, the brick layers (don’t take it as an offensive term, that’s not my intention), they have a strong focus on the technical component of the SharePoint environment, and although they can achieve greatness on their own, they can achieve so much more if they had guidance from someone with a broad understanding of SharePoint (not necessary focused on the technical side) with the ability to map a business problem to the SharePoint technology, that can engage with the business user and plan an approach that will achieve the greatness that SharePoint can provide.  They are the SharePoint Architect. The reason why I am focusing on this r...

I really don’t like the term “Best Practice”, because that implies that it can’t get any better, that’s not true as it’s the constant changing, modifying and improving of standards, methods, techniques and processes that makes best practice.  This is especially true in the IT world. I would like to enter this topic with a non-IT related example.  A few months ago, I was sick; this illness caused some internal imbalance that eventually lead to a high build-up of wax in my one ear.  It was so bad, my ear was completely blocked, and it remained blocked for days.  I had to go to the doctor. I was expecting the doctor to use some special ear-scope to find the wax build-up and then pluck it out with a tweezer or any other thin long medical device, it seems like the obvious solution, it would be quick and effective.   Instead, the doctor poured warm, soapy water into my ear, she poured and poured into the ear for about 1 and a half hours until the wax started t...