I am pleased to present to you a new frontier of software development that will greatly enhance your code quality: gitgud, the site for aggressive code reviews.
With gitgud, you are no longer tethered to what the development community considers "appropriate". It's a new way of getting your code reviewed. You can see instantly what other developers really think about your code quality without their opinions getting filtered by politeness and political correctness. All comments are anonymous so everyone is free from backlash and can freely express themselves about how truly horrific your code is.
By taking advantage of the aggressive and unfiltered code reviews, you are able to get to the center of your code quality issues and get them fixed quickly. You are able to "gitgud" at being a developer.
- Fully anonymous comments. Don't worry about being nice or holding back your opinions – it won't be tracked back to you.
- Includes options for text size and font colors (Note: currently only black, red, and rainbow have been implemented).
- Emoji Support. Let everyone know your "feelings" with rage and poop faces.
Author's Note: This post is satire and shouldn't be taken too seriously. The code review examples above should be treated as what NOT to do when you are given the opportunity to review some code. Below, I'll list some good code review practices that you can follow instead.
Some Best Practices for a Successful Code Review
Nothing shuts down motivation faster than reading negative comments. Keep your comments focused on what could make the code better, not only what the code is doing wrong. Explaining why it is not ideal is acceptable, as long as you can provide an alternative and explain why the alternative is better.
Use code reviews as a communication tool.
Oftentimes, developers can live in their little code bubbles and never look at all the code around them. By requesting code reviews, you are letting others into your bubble and letting people learn from what you’ve written. Alternatively, you can learn tips from developers who have done similar tasks in the past. Have you ever written a hundred lines of code only to find out later that there was a function built into your framework that did the exact same thing? These are the kind of tips you love to get from code reviews.
Leave your ego at the door.
Code reviews are not the place for flaunting how good of a developer you think you are or for shaming other to make yourself feel better. Every single developer has room for improvement. Even great developers have bad days with bad code. When receiving a code review, you should remember that is constructive criticism - it’s meant to make the code better. It is not a personal attack on your perceived development prowess.