Except SharePoint does store history and you can search it. And no need to create a second Beta1 and Beta2 folder when you can just mark documents as release = Beta1 or release = Beta2.
Except SharePoint does store history and you can search it. And no need to create a second Beta1 and Beta2 folder when you can just mark documents as release = Beta1 or release = Beta2.
And getting history out was, to put it mildly, a pain in the rear. Something I could do in five seconds became a nightmare of bad web UI.
Anyway, the devs in my group had a rule of keeping docs in the source depots, and we never lost anything. Poor other groups, we saw them lose important design documents when IT decided that the two year old SP wasn't being used anymore and got recycled. Wow.
Maybe SP does all that whizzy stuff. I just saw it being unutterably stupid, slow and unreliable in practice.
I have seen SharePoint installations at big corporations and they are horrible.
In one case there was a central SharePoint group that has commissioned the sites. So we had a highly restricted, utterly gutted and badly corporate styled thing that was practically useless.
Add to that that there was a weird mix of public and enterprise editions (which cost a bunch of money and were frowned upon by the org unit).
In this environment you can sit back and watch productivity and common sense being choked to death. Enterprise is a weird place.
Every time I've seen share point used, everyone described it the same way. Its where documents go to die.
So far at the current gig a share point "upgrade" has meant that all our fun use of the old install is useless. All of the sudden wikis look more useful.
Burn me once and all that. Oh and search, yeah that search is about as useful as altavista was back in the day.
Will someone please kill sharepoint already?
Let that sink in for a moment.
It does until it doesn't. Just like "Plays for Sure(TM)," also from MS, worked until it didn't.
Are you referring to unintended technical defects or DRM?
By all means. How do they know when they're done learning it? It's by definition difficult to tell the difference between missing functionality and hard-to-discover functionality.