Programming achievements

At insane programming i found the following list of programming achievements.

I do find that a funny idea, but i think these achievements have to be devided into a "good" and "bad" list, even if you are not a fan of Uncle Bob you can see that some (the bad ones) achievements are not desirable to achieve.
So i think its a fun way to see progress in a, otherwise, stuck project. But to be objective these achievements should be awarded by a colleague or the team at all. Like in a scrum/daily kanban meeting.  
I know it should not be part of any such meeting to make a code review. It should be the responsibility of a person dedicated to code quality. 
In small teams it is difficult to find someone who has enough free resources to do this. But in bigger teams this should be possible.

And the achievements can be announced by this person, at the daily meetings for the last day. So the code gets reviewed in a timely manner. And the daily meeting will not be over stretched, by just giving out the list of achievements.

Are you using it or wasting?

I have found this on bustr.tumblr.com and it is so true, first i thought it was this thing where you get every day the double amount of money from the day before starting with 1 $,€,Yen,Pound what ever. But it turned out to be much more serious and not theoretical at all.