Also, it would yell loudly about who you were, where you were going and who you were going to meet there. There’d be a switch to turn that off. It would be located behind the catalytic converter on the underside of the car, and would be functional only when the car was moving at freeway speeds.
* * *
An interesting conversation unfolded after this first appeared on ReadWriteWeb. Here’s what I wrote there:
For those of us who develop apps or manage engagement strategy, is there any platform more infuriating, any terrain less stable, any regime more prone to arbitrary and capricious rule changes than Facebook?
Goodbye “fans”; hello “like”. Goodbye boxes; hello profile tabs. Goodbye contests-with-dairy-products-as-a-prize; hello you-can’t-have-contests-with-dairy-products-as-a-prize.
I’ll say this much: My work in Facebook has allowed me to better embrace the impermanence of all things.
A commenter suggested this is a radical field, change is to be expected, and (to paraphrase) roll with it, dude. I replied (grumpily) that “constant incremental Agile-style change, I can cope with. More significant change based on some kind of rationale or, better yet, roadmap, I can embrace. But for years, Facebook has been notorious for dropping bombshells from out of the blue, and making unannounced or poorly document under-the-hood changes that break apps and make developers’ lives hell.”
Can you tell I carry a grudge from the promotion guidelines fiasco?
Anyway, what do you think? Do I need to lighten up and embrace Facebook’s turbulence, even when clients’ budgets are on the line? Or is that just giving in to (quote from that same reply) to “disregard for customer, user and developer communities”?