> Google does give a lot of love to developers.

That simply isn't true. They have support for some very specific areas which they consider of specific importance (e.g. Android), for the rest you're left to rot.

> Perhaps they do not have a corresponding relations team focused on operations support.

This has nothing to do with ops, it's a developer needing a raise in his apps requests quota.

The core areas can have the opposite problem almost. The Adwords API has moved pretty quickly but they are also quick to remove things. Most stuff built in early 2012 would have had to be updated for changed/ removed features by now.

I admit I haven't really traveled much on the less beaten paths. From the quality of what I have seen, I thought they must have policies for the minimum acceptable quality of all the public facing services to developers.

On the other hand, I am happy that even the big G cannot afford to cover all fronts. It means, there is still room for new players to grow and do well in those areas.

> look at the quality of their API documentations twitch maybe it's a personality clash, but I can't stand Google's documentation style, it's not well explained or laid out.

I know they have one group dedicated to the Android Source and they constantly answer questions related to development on their Google Group and elsewhere (like twitter). AOSP related stuff mostly comes off as good will towards the community as it's mostly those of us modding the source for ourselves and others in the community that are asking the questions.

I have looked it the quality of Google API'S its horrible only partially complete and totally lacking in meaningful documentation.

If some one came to me saying my employer is saying I am a poor performer and trying to sack me and gave the Google apis's and its documentation as an example I would have sympathies with the employer.