> When the dust settles, he'll give this idea another try.
This was my reaction when the word "feature" was still used in the apology. If it creates risk or user unhappiness, we call it a bug, not a feature. It's like calling mitigations for spectre from Intel a "generous rollback of performance features".
> Basically, he should've created a clueless VP of business relations or something of that sort
reminded by of the Gervais principle which I learned about from this nice article
The feature is public profiles, and I for one think it’s a neat idea to make a better alternative to LinkedIn for developers. This whole mess was not about the feature, but the way it was going to be rolled out at short notice to everybody who hadn’t explicitly turned it off, which is very different. I think Ammon himself put it best:
> I still believe there's a need for something like this. But to release it as a default public feature was not just a major mistake, it was a betrayal.
This was my reaction when the word "feature" was still used in the apology. If it creates risk or user unhappiness, we call it a bug, not a feature. It's like calling mitigations for spectre from Intel a "generous rollback of performance features".
> Basically, he should've created a clueless VP of business relations or something of that sort
reminded by of the Gervais principle which I learned about from this nice article
https://www.ribbonfarm.com/2009/10/07/the-gervais-principle-...