Code Reviews are Scary 😱👻
Code Reviews tend to strike fear into the hearts of junior devs and fill them with dread. If you're unfamiliar, Code Reviews are the approval process which your code goes through to make it into production. Your peers site down and review what you've written to make sure it's up to par with the rest of the code in the project.
If you're a junior developer or new on a team, code reviews can be a stressful process. We've certainly been frustrated by code reviews ourselves (looking at you, variable names).
This week we talk to Marko Markovich,the Backend Bear, about his experiences from the other side of the table as a senior engineer and team lead. We talk about do's and don'ts of code reviews, as well as their importance for the codebase and education of the engineers working on it.
Marko Markovich is a 10+ year software engineer with experience in C#, .NET, Android, and Java. Outside of work, Marko is the bassist and vocalist for a Tampa, FL metal band, and host of the Backend Bear Podcas where he talks about programming, developer life, and shares his knowledge about clean code and development.
- 1:35 - Intro
- 3:14 - "What is a Code Review?"
8:59 - In-person code reviews vs remote
- Naming variables
- 14:17 - Code standards/Style Guides at your company
- 16:15 - Why code standards are crucial and not 'nit-picking'
- 17:45 - Clean Code and Uncle Bob
- 24:21 - Rejecting code multiple times in a code review
- 29:42 - The Four Ways developers respond to code reviews
- 34:04 - Being scared of your code reviewer
- 39:46 - What programmers did before version control
- 41:10 - Design Patterns
- 43:42 - How to avoid 'argument soup' in methods
- 45:24 - Constructive vs Destructive Criticism
- 54:19 - The importance of communication for developers
58:49 - The Backend Bear Podcast 🎸
1:01:54 - Nerd Minute!