DO NOT write code if you don't have to.
I am a developer and I love coding. However, I find that not to write code, when the requirements can be fulfilled using OOB, is the way to make a SharePoint development project successful.
Yes, go codeless in a SharePoint development project.
Here are pros for going OOB:
- No need to write code
- No need to debug code
- No need to test code
- No need to optimize code, such as cache, log, exception handling, etc.
- Easier to understand (not always)
- Easier to deploy (not always)
- Shorter development cycle
- Save time and $
And of course there are cons:
- Harder to debug and test
- Limited options for optimization
- May not be feasible
- May be harder to deploy
Future of the SharePoint is OOB only, Sandbox solutions in SharePoint 2010 is the first step towards it.
There are certainly a lot more details to take into consideration, but thanks for sharing this post. SharePoint Consulting can provide a business with custom web parts and administrative tools.
ReplyDeleteNice post. I learn something more challenging on different blogs everyday. It will always be stimulating to read content from other writers and practice a little something from their store. I’d prefer to use some with the content on my blog whether you don’t mind. Natually I’ll give you a link on your web blog. Thanks for sharing.
ReplyDelete