Code reviews (see Chapter 9) are often a learning opportunity for both author(s) and reviewer(s). For example, a reviewer’s suggestion might introduce the author to a new testing pattern, or a reviewer might learn of a new library by seeing the author use it in their code. Google standardizes mentoring through code review with the readability process, as detailed in the case study at the end of this chapter.
I guess this is a good time to plug pair programming.
Two people sitting down together to code is a great way to learn and teach. As anyone who's done any sort of teaching knows, the act of teaching — or even just the prep/attempt at — often results in the teacher learning, too.
