Code reviews are always tricky because so much personality stuff can get involved if they aren't handled properly.
I'm sure if people follow this type of code review approach, it's going to benefit all the involved parties: the developer, reviewer and also the organization.
Thanks Saurabh! I believe these guidelines provide developers with a clear understanding of the purpose of this process and help them recognize that their comments have a broader impact beyond just the author. Loved your article 🙌
Good article, crisp and precise. Its always about learning new things from review. Its a way to teach juniors as well about logical parts of application how it can improved. It can be in terms of code refactoring as well on how to write better code.
Excellent tips Akos.
Code reviews are always tricky because so much personality stuff can get involved if they aren't handled properly.
I'm sure if people follow this type of code review approach, it's going to benefit all the involved parties: the developer, reviewer and also the organization.
Also, thanks for the mention!
Thanks Saurabh! I believe these guidelines provide developers with a clear understanding of the purpose of this process and help them recognize that their comments have a broader impact beyond just the author. Loved your article 🙌
Good article, crisp and precise. Its always about learning new things from review. Its a way to teach juniors as well about logical parts of application how it can improved. It can be in terms of code refactoring as well on how to write better code.
Thanks, Jayesh! Glad you liked the article! 🤜🤛