Versatile software engineer with a background in .NET consulting and CMS development. Working on regaining my embedded development skills to get more involved with IoT opportunities.
The primary purpose of code reviews, in my opinion, is to transfer knowledge. A developer gets a chance to walk someone else through their world. It's more efficient than trying to predict what team members will find relevant and it encourages a sense of shared ownership that further motivates team members to stick with the discipline, open-mindedness, and gentle spirit of inquisition.
Hi Scott. I believe you are right. Code reviews are an opportunity to transfer knowledge (even though the primary purpose is IMO to improve the quality of the deliverable). My view is that we should find ways to share that knowledge widely, among all the developers who might benefit from it within the team and the organization. Transferring knowledge to one developer is useful; sharing in with the team actually moves the needle in terms of team productivity.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The primary purpose of code reviews, in my opinion, is to transfer knowledge. A developer gets a chance to walk someone else through their world. It's more efficient than trying to predict what team members will find relevant and it encourages a sense of shared ownership that further motivates team members to stick with the discipline, open-mindedness, and gentle spirit of inquisition.
Hi Scott. I believe you are right. Code reviews are an opportunity to transfer knowledge (even though the primary purpose is IMO to improve the quality of the deliverable). My view is that we should find ways to share that knowledge widely, among all the developers who might benefit from it within the team and the organization. Transferring knowledge to one developer is useful; sharing in with the team actually moves the needle in terms of team productivity.