Given that Visual Studio underlines all your compilation errors and lists them in the Error List as you write your code, I don't see how this would work.
It would be part of the upcoming Hardcore mode, in which not only are intellisense and on-the-fly error checking disabled, but if your code fails to compile first time, it deletes the entire source tree.
I found "Hardcore" more appropriate; reminds me of Diablo 2's Hardcore mode where your character can't be recovered after any single death. "Nightmare" takes me back to Doom where it was just a harder mode, without the extra "permanent death" rule.
Sorry, that's my pedantry out of the way for the morning :)
Still encourages in the sense of wanting to obtain all of them, which can be pretty powerful, although I'm sure anyone would just do those for jokes (you could even write a script to win those achievements for you! :).
If I saw achievements in my text editor though, I'd feel it's a bit patronizing personally. What I want in new releases is to help me do my work faster and better, anything else just gets in the way.
This ongoing trend of "gamification" is starting to drive me up the wall. Seems like some brainiac in marketing won some battle to sink their claws into the VS team. And I feel bad for them, because I'd hope they'd want to be spending their team actually improving VS (which is still an excellent IDE) instead of adding a layer of crapola lipstick.
Reminds me of the time I was working on a .net project and the lead developer wired up a call in the OnApplicationError method to log the machine name origin of each error to a database. Every week he would hand out an award to the person with the most errors.
The interesting part was when he did the same thing for the bug tracker, the list was inverted. Those with more errors in development had fewer bugs in QA.
Thinking back on all the colleagues I've had who seemed to believe that 'debugging' is just another word for 'getting it to compile', that inverse relationship does not surprise me at all.
I don't understand the leaderboard aspect of it because, if I'm reading the article correctly, each of the achievements is a one-off, which means that the leaderboard will quickly be dominated with a few developers who happened to hit all of the achievements.
Also, a lot of these rely on analysis of the code. In that case, will every team member who has the code checked out receive every award that is unlocked by the project?
These seem to be sending mixed messages. Some of these very much seem to be lampooning certain negative behaviors, some of them seem to be encouraging certain positive behaviors. Overall it seems to be ridiculous and an unhelpful distraction.
Wow. Thanks Microsoft for cluttering up yet another product with more UI Craptastic.
Honestly I know it's all done in fun but really, people using the product are trying to concentrate, they're trying to solve really hard problems and you're going to pop up some crap telling them they achieved some stupid "award".
You morons, this is akin to the marketing joker in the office that annoys alls the programmers by interrupting them all day with stupid jokes, you know the guy, he's the one you want to punch in the face everyday.
And to the guys that actually coded this up, learn to say no. Put your job on the line; fuck it it's not worth making the world a worse place by adding this kinda crap to a developer tool.
- Field Master: Have 100 fields in a single class.
- Overload: More than 10 overloads of a method.
- Potty Mouth: Use 5 different curse words in a file.
These are funny, but they miss what achievements are good for - encouraging new users to adopt good behaviours.