Yup...it's bad. Part of the problem I've had which I'm guessing is some of the posters issue is that larger companies have their Sharepoint group. DBAs pretty much stay out of it except for builds (and finding the requirements all over in a few different docs) and only when there are problems. I remember when I did add some jobs and indexes. And sometime later they had some RBS issues so they opened a ticket. The support engineer told them he didn't have to support it due to the changes that had been made outside of "Sharepoint recommendations" - even though it had nothing to do with the issues. He removed the jobs and most of the indexes and I later had a fun meeting involving the "stakeholders" and all the politics. Fortunately the manager was good and that ended most of our "troubleshooting" support for Sharepoint. 

It's pretty easy to find a ton of things to fix in that mess because it is so flipping bad but the larger the farm, the more issues there are and unfortunately the more politics. Kind of a bad mix. I pretty much try to stay away unless its relatively smaller one. And those aren't too problematic. It's still ugly in places but you can often throw some hardware at it to mitigate the issues. And political apps get money so often its all good there. 

Now I have that Sharepoint nightmare feeling.....

Sue