Recently, I’ve been challenged to think more about my pair programming style and how I share the responsibilities of driving and navigating with my pair. Inspired by Marlena Compton’s post different ways to pair.
Using Jenn Schiffer’s online 8-bit art maker, I quickly drew some icons to better represent the various techniques that she proposed to show to my team.
Feel free to use these images for educational purposes and to let me know via Twitter!
The classic Ping Pong technique where one person writes a failing test and then the other tries to implement the minimum necessary code in order to pass the test.
This can also be implemented with non-TDD where one person writes an implementation and the other tries to refactor it into something simpler.
Switch on Tasks
Switch on Google
Any time the thought pops into a pair’s head that they would like to research something further like a bug or documentation, the pair should switch to avoid the temptation to research on the side.