Comment Re:More info, please... (Score 1) 365
He doesn't, actually.
I do, actually.
My experience was with Sharepoint in 2005 (before I started at Google). Small company (about 100 employees). Over the previous two years, the project team had created an extensive development info repository with TWiki, but the new VP Dev thought that we should switch from mixed Linux/MS to MS only. So they asked all of the developers to move everything over to a new Sharepoint deployment, under the guidance of a MS certified Sharepoint consultant (never knew exactly what certification they guy had).
This basically meant taking each page from the Wiki, creating a Word doc that said something similar (without the effortless linking of a wiki), and uploading it into the Sharepoint knowledge base. There was a very cumbersome checkout/edit/checkin process which seemed to take the worst of the issues from VSS and bless them with new life. The whole thing was awful and ended up being abandoned in favor of the old wiki within a year. We were also trying to take the core product (contract management) and move it so that it could be accessed via a Sharepoint interface. The API's were worse than the document management system, and this architectural 180 was also abandoned within a year as completely untenable.
I never did see an useful/informative definition for what Sharepoint was, so a document store that couldn't quite be a wiki and several attempts to improve the collaborative interaction, was what I experienced. It wasn't very impressive.
BTW, I'm not anti-MS, just have nothing good to say about Sharepoint. I really like