When achievements were first released for the Medic in Team Fortress 2, players who weren't Medics suffered. Some of the achievements require the Medic to either become an offensive player, or intentionally make bad choices. The more players tried for achievements, the worse your team did. For future achievements releases, Valve changed the focus of achievements to reward class strengths, showcase new features, reward good behavior, or highlight awesome events.
A Visual Studio achievement like "Job Security" would be terrible. It just encourages bad practices. I don't want to fix a bug in a 30-line Linq query, or understand if it does exactly what you say it does. In fact, its opposite is a better achievement: "If You Linq, You Will Miss It: Write 100 Linq queries with 3 lines or fewer." It encourages users to use a great feature, doesn't punish them if they find a case where they absolutely need to write something longer, and encourages a good habit.
That being said, some of them were also good. I could see Visual Studio using "Gimme back my ASM" or "The Academic". Some also had a Valve-style personality, like "Shotgun Debugging" or "Rage Quit."
For anyone wondering what "Whoooooosh" is supposed to mean, it is a meme for "you missed the point". It is usually used of the topic was sarcasm or irony and someone did not realise that.
The article was not as good as I expected. There are arguments for achievement-like things in VS, for example unit test coverage. This article was aimless and negative.
Actually, the achievements mimicked gaming achievements fairly well. A mix of goofy, funny, ridiculous, and painful. I don't see a problem with that at all. As a humor piece, which is what it is supposed to be, it succeeds.
When achievements were first released for the Medic in Team Fortress 2, players who weren't Medics suffered. Some of the achievements require the Medic to either become an offensive player, or intentionally make bad choices. The more players tried for achievements, the worse your team did. For future achievements releases, Valve changed the focus of achievements to reward class strengths, showcase new features, reward good behavior, or highlight awesome events.
A Visual Studio achievement like "Job Security" would be terrible. It just encourages bad practices. I don't want to fix a bug in a 30-line Linq query, or understand if it does exactly what you say it does. In fact, its opposite is a better achievement: "If You Linq, You Will Miss It: Write 100 Linq queries with 3 lines or fewer." It encourages users to use a great feature, doesn't punish them if they find a case where they absolutely need to write something longer, and encourages a good habit.
That being said, some of them were also good. I could see Visual Studio using "Gimme back my ASM" or "The Academic". Some also had a Valve-style personality, like "Shotgun Debugging" or "Rage Quit."