Here we are, with another year [almost] behind us. 2014 has been very, very special on Code Review, and that has been completely because of you.
2014 was ...glittering. We've put Code Review on the Stack Exchange map; in 2015, we're entering the big league of full-grown, graduated sites.
What events made 2014 a year to remember on CR?
In large part thanks to significant, sustained, and far-reaching growth (image taken at around that time):
We don't just review code around here. We write it too.
A lot of the regulars in the 2nd Monitor began working on a card game called Cardshifter in August. A dedicated chat room was created. It is sourced using Java 8 and related technologies.
Over in the VBA chatroom, we began working on an ambitious project to bring VBA's IDE into this century. This was also born out of a strong desire for a good Unit Testing framework for VBA.
Both projects are very active and we have Code Review to thank for bringing the contributors together.
When Jamal posted his first Java question, a fizzbuzz, something happened in The 2nd Monitor, and then July saw a fizzbuzz implementation in just about every programming language out there...
The invasion continued through August, and in September a Mug went on to smoke the manual and created the lolcode tag after implementing fizzbuzz in LOLCODE. That was fun and all, and resulted in a discussion about reviewing esoteric languages, where all points of view were expressed and debated.
As a result of all this, Code Review has 55 fizzbuzz questions as of this writing.
...and 40 were asked in 2014... and 31 of them followed Jamal's post in July.
Back in March, Code Review got two new moderators that turned out to be very active. It has always been easy to get in contact with them in our chatroom, and they have done a great job in contacting users through chat whenever something was up.
Two new technologies introduced this year have transformed the face of Code Review.
At the request of @VedranŠego, and with broad support from the CR community, we gathered enough evidence to convince Stack Exchange staff of the benefits of MathJax to the site. On April 7, MathJax was enabled!
In contrast to the hard work we had to do to earn MathJax, the Stack Snippets feature came as a bit of a present. In August, Stack Exchange developers informed us of the new feature that they had developed. It didn't take much argument to convince them that piloting a feature on a beta site was a good idea.
Rather than naming specific posts here that have made good use of MathJax and Stack Snippets, I have proposed them as categories for Best of Code Review 2014, so that we can all participate in picking out the best posts.
