Win-an-eBook Wednesdays is a small three day contest that we hold every week. The Prize? An O’reilly eBook for your choice! Furthermore, if you win, you also get the chance to ask the community whatever question you want and be the judge for next week’s contest!
The only thing you have to do to enter is answer the following question: How do you say NO in a SharePoint world?
This week’s judge is Stephen Tierney , winner of last week’s contest( He got the Microsoft SharePoint 2013 Developer Reference eBook).
Stephen’s Comments:
Sometimes as a Developer, Admin, Manager or End User we have to say No. SharePoint is a platform so it can do anything right? Sometimes the requests are a little out there and you have to say No to a feature, tool or even push back as an end user. How do you do that without being the bad one?
You have until Friday 26th (10pm GMT) to answer this question!
Unless it violates a supportability statement, I generally do not. We heavily review 3rd party code (even if that is internal, but outside of IT) that is farm-level (sandbox solutions are not reviewed as SharePoint has other ways to control those). I’ll always steer people in a suggested direction, however.
People/Businesses who don’t want to learn the value of SharePoint but just want to implement cause everybody else is doing so and are saying that SharePoint is no different then other Software systems in the World. I say ‘NO’ until they agree to learn the value SharePoint adds in our daily business.
I don’t! I hide behind my new-ness and make my boss do it.
As cowardly as this is, it really is the best way for me to handle it right now. I still don’t fully know yet what SharePoint can and can’t do. Compared to the last platform I worked with, things that used to be hard it can do quite easily, and things I think it should be able to do easily are completely impossible. But even “impossible” is not the final word, since some of those things can be accomplished – with varying degrees of difficulty – through the use of additional tools like JQuery. So until I can get a little bit more experience (and with experience comes confidence) under my belt, I’m really better off keeping my mouth shut and letting my boss tell our customers what is and isn’t reasonable for our projects.
A bit of background here- In one of our SharePoint environment, people with authoring access are creating pages on the fly to try out stuff and to play around. I was completely thrown away on seeing this but this has been going on for a long time 🙂
I had to say NO as environment admin in a polite way. So i had to create a new testing environment for them to play around to avoid this.
