Why I am letting my Google IO invitation expire
Hi, [REDACTED]. Thanks for writing to express your concern about my failure to redeem my Google IO promo code. It's kind of a funny story. — I received a Google IO invitation (copied and pasted below) but didn't follow …
Context & Ripple Effects
Jeffrey Zeldman's decision to let a Google I/O invitation and promo code lapse lands three months after MG Siegler's open letter to Google+, part of a stretch in which prominent independent bloggers have been publishing their disappointments with Google rather than quietly moving on. The pickup by parislemon and others within a day shows how little reach it takes for one person's non-attendance to become a story.
First-order effects
- Zeldman forgoes his seat at I/O, and Google loses one visible member of its developer audience at no cost to him beyond an expired promo code.
Second-order effects
- Once declining an invitation is written up rather than kept private, attendance itself becomes a public statement — other invited developers now weigh whether showing up reads as an endorsement of the company.
Third-order effects
- Developer conferences drift from scarce perks toward reputational transactions, where organizers have to earn each high-profile attendee rather than assume an invite guarantees presence — a dynamic Google's own long history of critic-baiting moments, from the 2007 Founders' Awards cuts onward, keeps feeding.
The trend: Developer relations are shifting from invitation-driven access to accountability, where prominent developers' decisions to attend or skip a company's flagship event are themselves commentary.