Today I share my final thoughts on code review. Code review is probably the best time to do your learning together in a given team. More often than not, its the only formal time for developers to share knowledge and grow each other.
Junior developers may fall into a trap where they get defensive in code review or feel it's an attack on them. Not only is that just not true, but they're also missing a huge opportunity to learn. Feel free to ask more questions and any decent senior engineer should happily explain comments or critiques further.
By listening, understanding and reflecting on your code review feedback (or any feedback for that matter) you'll learn a lot in order to be a better developer.
Heads up: As with any terse bit of advice, there will be exceptions of course, and subtleties and nuance that can't possibly be captured in a Byte of Wisdom. This has been what I've experienced, I'd love to hear yours in the comments too!
You can catch up with all the other bytes at http://bytesofwisdom.com/
Top comments (0)