It's interesting to read about what technologies companies use, how they use them etc. Not about things you could see if you flicked over to Martha Stewart.
Once the knowledge of what works and what doesn't is wide spread enough, it's no longer an issue, and you can write a feel good fluff piece about it without getting into the gritty details, and get most all of the beneficial karma from fans and community, without giving away too many tips to rivals. I'd argue that the reason it's not kosher to give away secrets of how you did something at a big place is that once you get big enough, there's always someone around who can argue that the secrets are inestimably valuable, and the benefits in the form of developing community are paltry by comparison.
Sure, the competitor may then bypass all your discussions and go straight to the "solution", but I'd argue the discussions and considered thought puts your company in a far better position to out-maneuver the competitor in the future for the very reason that you've been thinking about the problem domain much longer, and in a much broader sense. Getting to the result without the understanding doesn't yield long-term success.
We didn't ship and then retract. We just started with an extremely small seed community and are rolling it out very slowly over time.
I wish there were more of a culture of insider writing while the events were going on. When Facebook pushed Questions and then retracted it, I'd love to see a blog post about "Yeah, we pushed Questions because it rocked but once we shipped it everything exploded and shit went crazy. Here are the details and what we learned from it. [...]" That's far more interesting to me, and really compelling to someone looking to become a Facebook engineer.
Unfortunately, once you grow to a certain level, those things are no longer kosher. Plain talk is discouraged in an era of Corporate Speak. It's unfortunate.
But cheers on this guy's three years though.