Some say that learning is a team effort, and pair programming makes that an explicit part of learning how to code. Here’s how it works, the pros and cons.<\/p>\n
There are no rubrics or packages needed to teach coding with pair programming. This is a practice that comes from software development where two individuals work together on coding. They trade off on roles, which are: <\/p>\n
The driver is the one “behind the wheel,” or the keyboard as it were. The driver pushes ahead toward the destination, writing, running and inspecting the code. <\/p>\n
We’re mostly used to the “driver” role because that’s what we do when we work by ourselves, right? We push ahead toward our goals.<\/p>\n
What makes pair programming different is the presence of a navigator. This person is in co-pilot position, making sure the driver stays on a good course. They help the driver make adjustments to the route mid-journey. This of this as a real-time code review. <\/p>\n
The driver and navigator are equally in charge of the output! Neither role is more important. The driver and navigator also changes places, perhaps trading off on days or activities while learning. <\/p>\n