How To Review Code As A Junior Developer
tl;dr: (1) "If something is not clear to you, it probably isn’t clear to everyone," so ask questions. (2) Calibrate feedback - "work to cater recommendations to the individual." (3) Emulate others "by observing how your coworkers review code, you can learn what to pay attention to when you’re writing code.
featured in #238
How To Make Your Code Reviewer Fall In Love With You
tl;dr: Many tips, including review your own code first, write a clear changelist description to provide context, conduct your review after your code passes all automated tests, and more.
featured in #218
Code Review - From Good To Great
tl;dr: 8 recommendations on creating a better process including more face-to-face interactions with less code review tools when possible, and using review as a means to mentor.
featured in #195
Five Code Review Antipatterns
tl;dr: (1) Nit-picking (2) inconsistent feedback (3) last-minute design changes (4) ping-pong reviews (5) ghost reviewer.
featured in #182
Radical Candor: Software Edition
tl;dr: A management style of communication that's "kind and clear, specific and sincere" is applied to both design and code reviews here.
You can bypass the paywall by clicking the link in this tweet.
featured in #169
10 Tips For Reviewing Code You Don't Like
tl;dr: Avoid hyperbolic or bombastic assertions, argument strategies, elitist or demeaning language, and constructs like “obviously” and “why don’t you just…”. Use clear, factual statements supportive language, ask questions, and move things forward.
featured in #148
Code Reviews at Microsoft
tl;dr: Approx 40% of engineers code review at least one a day at Microsoft. This outlines the process and tools used, which are applicable to orgs of all sizes.
featured in #142