Published in


5 Common Mistakes Even Seasoned Developers Make on a Code Review

Here are the bad habits you should avoid in a code review process

Photo by Tima Miroshnichenko from Pexels — Edits by author

You raise the PR. And no one reviews code for days.

You constantly check the status, but still no code review comments.




Everything connected with Tech & Code. Follow to join our 900K+ monthly readers

Recommended from Medium

Agile Misunderstandings: Resource Planning

A perfect duplicate or how to send an email with a spoofed invoice’s content

Mr. Karan Shakya: On starting a career as a Frontend Developer

Techniques to Cut Gas Costs for Your Dapps

Watson Knowledge Studio Announces Multiple Preannotators Feature

Debugging Web Applications on iOS with Windows 10

Taco Wrap Up: April

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Miloš Živković

Miloš Živković

Java and dev lifestyle stories. Subscribe for limitless reading: Check out some of my e-books:

More from Medium

What Experienced Developers Get Wrong about Code Reviews

Developers doing code review with wrong approach. Probably using WTFM metric to do code reviews.

“Don’t obey the Testing Goat!” — When Test-Driven-Development isn’t the Answer

Max: “assertFalse? Should it not be assertTrue?”. Alex: “With assertTrue the test went red”.

10 Hints to Avoid Over-complexity in Software Projects

lost in space

SOLID principles and common misconceptions