When one teaches two learn
Claudio and I gave a talk on WebUI testing last TechFest (link pending). While reflecting on it, I uncovered another valuable lesson I learned. At the time, We had reached a point where only UI work remained. So Claudio and I paired up.
We started by sculpting GWT cases for the code. This provided an opportunity for me to explain the functions of the existing Thunk. While teaching Claudio about some of the 'how' the framework worked, I learned more about it myself. For example, I gained a new respect for the synchronous nature of
dispatch(). In particular, the impact of long running Thunks stood out.
As I reflect on this experience, one phrase repeats itself in my mind: 'When One teaches Two learn'. As I mentioned, my own understanding of Redux improved. By explaining its operations and how affected the Thunk to Claudio, I learned the framework at a deeper level.
When I discussed this observation with him, he shared a practice he had developed. He looks for someone to teach a concept to as soon as he learns it. For one thing, being so close to having learned it he remembers what it is like to not know. Moreover, he gains a deeper understanding through teaching it than he started with.
Having now experience this phenomena, teaching-after-learning is a most excellent practice! I plan to look for ways to share my knowledge with others. And I hope that this brief dialog encourages you likewise. 'Let us share the light of knowledge, as it will kindle our own flame to even greater incandescence!'