Code review is the process of having another developer examine your code before it gets merged into the main codebase. It's like having someone proofread your essay, except instead of checking for grammar mistakes, they're making sure your code isn't a steaming pile of 💩.

How to use it in a sentence

• "I can't push my brilliant new feature until it passes code review, so I guess I'll just keep refreshing my email until I get the thumbs up."

• "Looks like my pull request got rejected in code review again. Apparently, naming variables after Game of Thrones characters isn't considered 'best practice'."

If you actually want to learn more...

• On Pair Programming - This article explains why code reviews alone aren't a great substitute for pair programming. Turns out having someone breathing down your neck while you code catches bugs faster than an asynchronous game of "spot the bug".

• Goto Fail, Heartbleed, and Unit Testing Culture - A deep dive into how code reviews and testing could have prevented major security vulnerabilities. Spoiler alert: more testing and reviews = less embarrassing hacks.

• 11 Best Practices for Peer Code Review - Some tips to make your code reviews less painful and more productive. TLDR: Keep your reviews small, focused and don't be a jerk.

Note: the Developer Dictionary is in Beta. Please direct feedback to skye@statsig.com.