After over a decade of working with everything in SharePoint and possessing the ability to configure just about anything using the SharePoint platform I have amassed the experience and skills required to refer to myself as an architect. I have sat and passed pretty much every Microsoft SharePoint exam that has been published so not only do I have a keen understanding of all the features and functionality of SharePoint I can also recommend a given approach over another taking into account such things as performance implications, scalability or knowing the recommended thresholds of SharePoint.
I have done the hard miles no doubt. Having been around SharePoint for over 12 years I have seen most things SharePoint throws up at you and SharePoint can be a cruel mistress at times. I maintain that no two SharePoint Farms are ever the same, indeed they are like fingerprints.
Like any SharePoint architect I possess experience in associated technologies such as Active Directory, ADFS, SQL Server to name but a few. Having the all round understanding of all the associated technologies has provided me the opportunity to work on numerous global SharePoint installations in both the public and private sector.
Being a SharePoint architect isn’t just about knowing that a list threshold limit is 5000 items, undoubtedly this is a prerequisite but being a SharePoint architect is so much more. As an architect you also need to have a solid understanding of how to glean the requirements from business users and then apply the proper components or technologies to solve the problem.
Having been around SharePoint for so long I must confess I started to get a little bored with the whole SharePoint story