The document proposes a "Code Review Drinking Game" where certain common code review occurrences trigger sips of a drink, such as using "Random" instead of "secureRandom", TODO comments, or merge conflicts in committed code. It includes drinking game rules for both Java and JavaScript code reviews. The goal is to have an entertaining way to conduct code reviews by turning typical issues into opportunities to drink.
4. The only valid measurement of code quality:
code
review
good code
(c) 2008 focus shift
5. The only valid measurement of code quality:
code
review
wtf
wtf
good code
(c) 2008 focus shift
6. The only valid measurement of code quality:
code
review
wtf
wtf
good code
wtf
wtf is
this shit
wtf
wtf
dude,
wtf!
code
review
bad code
(c) 2008 focus shift
7. [line 67]
Code Reviews be like:
why are you doing this?
«explains code»
no... as a profession?
8. Drinking
Game?
artist winks at
camera
bad joke by
country at
results
bad NOTe
12 points for
neighbour
presenter
changes
costume
presenter
flirts
5 people sing
on stage
wind machine
blows
choir whistles
artist without
shoes
artist looses
wardrobe
folklore
outfit
Finale Drinking Game 2016
1 sip 2 sips ad fundum
9. Java
1 sip 2 sips ad fundum
.net
code review
drinking
game