Code Review Metrics: WTFs/M
As a programmer it’s always fun to see the stuff that people come up with for code review metrics. What makes the code good, what makes it bad (all of which I think is relative to the person reviewing it because none of us can really agree on anything out in the programmer world, there’s agreeing with the bosses just so you can keep your job but knowing deep down in your heart that you really don’t agree and that there could possibly be a better way to do something than what they were proposing, but that’s really not agreeing, I digress.)
I was sent this little comic by my x-supervisor and I think any programmer will find it humorous.
orignally found on OSnews
And at the rate of all the disagreement that goes on between programmers, it might be completely valid of us to say that this is the only valid measurement of code quality. One of my coworkers and I completely agree that our code is awesome right up until we read through it and have to go fix it because we’re the ones sitting there going WTF long before it gets to the QA process.
Holy damn, that comic is hilarious. I am printing this out.
that might also go well with how well someone is playing certain video games. great cartoon
ah, like the more WTFs the worse the game is or something?