Ive only really started using SharePoint since Ive been contracting at my new place of work, and it seems pretty good to me.
I have two SP sites. One was inherited and maintained by my environment/configuration manager for my previous project, and the other I have been playing with in my spare time. Ive been advised that to use it properly, you start with one document library which acts as a bucket for all types of files, and then you use the metadata you give to each file to augment the many views you can setup in SP I prefer the traditional file/folder structure, though, which is what I have used for my new project SharePoint site
Ive been playing with the front page, and with a little help from nakedfrog, I managed to get the html table in the centre looking much better. I think it's great, I've just got to get my project team using it more instead of using it as a basic repository:
Agreed that SharePoint has huge potential, especially if you're willing to get into the business data integration side of things. With 2010's native integration of PerformancePoint, you can make some really powerful dashboards that pull data directly from different data sources across the enterprise.
SharePoint has been quite the success in being a single point from which all of our users can "get things done" - from end-users entering daily numbers and storing project-related files, to middle management viewing reports on today's numbers, to upper management viewing trends and risky projects via PerformancePoint 2007 scorecards.
The other nice thing about SharePoint from an IT side is that there's a spot for just about all types of IT people. As a framework, it provides a base to use all the latest MS technologies for coders. Keeping a large implementation running smoothly can call for a fulltime SharePoint architect to design metadata schema, permissions, etc. There's also the web development side there, using SharePoint designer to make custom templates and site modifications.