A Google developer and API evangelist, P., invites me to take a look at a new API. I reply that, instead, I'd like to discuss the GData APIs. P. thanks me for my interest in GData, and promises to try to connect me with someone.
A couple of days later I hear from S., on Google's "communication team." S. initiates the usual PR protocol: "Can you give me some details about the story you are working on and what information you'd like from Google?"
Sigh. I'm not working on a story, at least not yet, I'm just curious about GData. I can and will research it myself, but if you want to play a role in that process, trying to pin me down to a laundry list of questions won't help your cause. Just find me somebody who is passionate about GData, and who is allowed to discuss it.
But then S. turns up the heat. "Can you also please contact the communications team rather than going to the product folks directly so we can make sure your inquiry is routed to the appropriate party and answered in a timely fashion?"
Oh please. It was P. who wrote to me in the first place. I relayed my request through P. because I had a hunch that the "communications team" might not be tuned into GData. So I ignore the slapdown and merely reply to S.:
"I would like to talk to folks on the GData team about the APIs and their uses."
S., who let's recall is employed by the world's leading search engine, replies:
"What does Gdata refer to? We don't have a product called Gdata that I'm aware of....."
I am not making this up.
Another day passes, S. figures out how to Google GData, and writes back that an interview can be arranged, provided that I first enumerate my questions.
Never mind. I only have one question at this point. What planet are you living on?
Former URL: http://weblog.infoworld.com/udell/2006/06/03.html#a1461