I guess it was only a matter of time before games and programming met right at the very coalface of coding, and achievements found their toasty little ways into IDEs.
Among the list of achievements are counter-productive items, such as writing 20-letter class-level variables in one file, using goto keyword, and writing an enum with 30 fields. I'd like to counter that with a list of good coding practice achievements, but they simply aren't there; they mainly reward the use of Visual Studio's features. This is likely because judging what is good code is a subjective task at the best of times, and it is easier to automate the detection of bad code.This could be useful to educate new programmers on what to avoid, with something like "You've achieved goto usage, now never do it again", and links on why to avoid it.
I'd hate to be on the receiving end of some code that the author decided to use to go for the Scroll Bar Wizard, Job Security and Field Master trifecta.
Some would say that it is a long way from software engineering to journalism, others would correctly argue that it is a mere 10 metres according to the floor plan.During his first five years with CBS Interactive, Chris started his journalistic adventure in 2006 as the Editor of Builder AU after originally joining the company as a programmer.Leaving CBS Interactive in 2010 to follow his deep desire to study the snowdrifts and culinary delights of Canada, Chris based himself in Vancouver and paid for his new snowboarding and poutine cravings as a programmer for a lifestyle gaming startup.Chris returns to CBS in 2011 as the Editor of TechRepublic Australia determined to meld together his programming and journalistic tendencies once and for all.In his free time, Chris is often seen yelling at different operating systems for their own unique failures, avoiding the dreaded tech support calls from relatives, and conducting extensive studies of internets -- he claims he once read an entire one.