Here’s Why You’re Doing Code Review WRONG - Essential Software Engineer Skills

After years of working across multiple teams + companies, here are my best practices and tactics to have better code reviews. Code review is a fundamental part of every well run engineering team: any code written should get reviewed by a human who approves the change.

💌 Join our mailing list: techcareergrowth.substack.com/
🤖 Android app for Tech Career Growth: play.google.com/store/apps/details?id=com.randomap…
📱 iOS app for Tech Career Growth: apps.apple.com/app/id1605094641

My friend Curtis has a great course about code review which you can find here: curtiseinsmann.gumroad.com/l/code-review-course

➤ Slack community: join.slack.com/t/techcareergrowth/shared_invite/zt…
➤ LinkedIn community: www.linkedin.com/company/techcareergrowth/
➤ Connect with Alex: www.linkedin.com/in/alexander-chiou/

Hi! I’m Rahul, a software engineer and founder with a passion for teaching.
📹 YouTube: youtube.com/c/RahulPandeyRkp
📝 LinkedIn: www.linkedin.com/in/rpandey1234/
🐦 Twitter: twitter.com/rpandey1234
📸 Instagram: www.instagram.com/rpandey1234/
📂 Github: github.com/rpandey1234/

🎥 My YouTube Camera Gear - kit.co/rpandey1234/my-youtube-gear-2022

Timestamps:
0:00 - Intro
1:20 - Different company terminology for code changes
2:03 - Code review if you're new to a team/company
2:40 - Healthy code review -- too high level
3:14 - Healthy code review -- too low level
3:58 - Healthy code review -- sweet spot
4:51 - Best practice #1 - keep code changes small
5:37 - Best practice #2 - delegate work to the computer
6:37 - Best practice #3 - be proactive about getting feedback
7:27 - Best practice #4 - be aware of the back-and-forth

#TechCareerGrowth