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.
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 ...
Simon on 'Team Split' problem
Okay, maybe "one" more word.
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++, ...