Tag Info

Best of Code Review 2014 - Lots of Laughs category: Answer that makes the best use of humor to illustrate a point.

Best of Code Review 2014 - Exterminator category: Answer that points out the most interesting obscure bug in the original code

Best of Code Review 2014 - Best Title category: The question with the best title. (If the title was later added by someone else, be sure to credit the user who edited the title.)

Best of Code Review 2014 - Night and Day category: The most dramatic improvement (nominate both the question with the most hopeless code and the answer that cleans it up the best)

Best Newcomer (Answer) category: Best answer by a user who had not posted an answer before 2015.

Best Newcomer (Answer) category: Best answer by a user who had not posted an answer before 2016.

Not As Easy As It Looks category: Question that superficially appears simple but turns out to be more difficult than expected

Diplomat: Tough advice in an answer, delivered in the most tactful manner.

Diplomat category: Tough advice in an answer, delivered in the most tactful manner

Best Newcomer (Question) category: Best question by a user who had not posted a question before 2016.

Jamalizer* Award category, for question edits that turned bad questions into good ones. *see Jamalized

Lots of Laughs: Answer that makes the best use of humor to illustrate a point.

Night and Day: The most dramatic improvement (nominate both the question with the most hopeless code and the answer that cleans it up the best)

Gordian Knot Untied category: Most justified advice in an answer for taking a completely different approach from the code in the original question

Rags to Riches category: The rags-to-riches question that took the worst original code and made it shine like a polished gem

Diplomat: Tough advice in an answer, delivered in the most tactful manner

Exterminator: Answer that points out the most interesting obscure bug in the original code.

Best shortening Of course I am not talking about CodeGolf, this category aims to reward answers that given an absurdly long and bloated code in the question, shorten it significantly while retaining functionality and improving readibility at the same time.

Best Title category: The question with the best title. (If the title was later added by someone else, be sure to credit the user who edited the title.)

I'm nominating the following question: The right way to hang a man While the title could be considered somewhat dark, it's still a very unique and clever way of titling a question about Hangman, compared to the bland titles usually found in the hangman tag. The question has also accrued over 25 votes, more than 2500 views and is currently the top question ...

Stack Snippets category: The question, answer, or edit that makes the best use of Stack Snippets

Best Title category: The question with the best title. (If the title was later added by someone else, be sure to credit the user who edited the title.)

Nominating this answer to Easier user input in C++ There is more topics covered in the answer than lines of code in the question. All thoroughly developed, educational, and to the point. What more?

Best of Code Review 2013 — Night and Day category: The most dramatic improvement (nominate both the question with the most hopeless code and the answer that cleans it up the best)

MathJax category: Question, answer, or edit that makes the best use of MathJax

Simon on 'Team Split' problem One word: Rewafadhabihlgdity Okay, maybe "one" more word. Dontyoufinditabithardtoreadtext/codethatdoesntcontainanyspacesandappropriatepunctuation? These two "words" make the point clear about how readable the code was, and why it is good to use spacing.

Regularity in the “Rusty Towel of Mutual understanding” Author: Rolfl (revision 3) | answered This question also went to the Hot Network Questions and into the weekly CR newsletter the week it was posted. I think this was a great title because it's not only eye-catching and intriguing, it actually - believe it or not - says exactly what the post is about, ...

This answer by Quuxplusone to "Hybrid Lock Implementation (C++)" points out a nearly invisibly typo that breaks the whole thing. In the question, OP meant to write this->mFlag but wrote this>mFlag and of course, since in C++ this is just a pointer, everything compiles. That's one reason to avoid this-> qualifying member variables in C++, ...

One of the questions that I think drew the most attention this year due to its title is: How clean is my snow? As evidenced by the 10,000+ views and multiple answers, the title, which accurately describes the topic of the question, must have invoked in many of us who grew up in colder climates some childhood memories of freshly fallen, pure white snow.