Abstract
SharePoint has not yet reached its full potential. This is partly due to the time it takes to refine and perfect an application, but it is also due to the limitations and boundaries set for it by the technologies upon which it is dependent. SharePoint is bound by.NET, Windows, Active Directory, networks, latency, bandwidth, SQL Server, and the Internet, in no particular order. But the primary limiter of the potential of SharePoint by far is the decision makers who have responsibility for its planning, deployment, and maintenance. There are many perspectives you can take on why something is what it is; there are always many interrelated causes. While we can’t control the hardware, software, networking, and developmental limitations of the SharePoint platform, the actions of those who run it can make the greatest difference to its success or failure.
A principle is the expression of perfection, and as imperfect beings like us cannot practise perfection, we devise every moment limits of its compromise in practice. —Mohandas Gandhi
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2011 Stephen Cummins
About this chapter
Cite this chapter
Cummins, S. (2011). Best and Worst Practices. In: Pro SharePoint 2010 Disaster Recovery and High Availability. Apress. https://doi.org/10.1007/978-1-4302-3952-9_11
Download citation
DOI: https://doi.org/10.1007/978-1-4302-3952-9_11
Publisher Name: Apress
Print ISBN: 978-1-4302-3951-2
Online ISBN: 978-1-4302-3952-9
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)