This post serves as the continuation of a previously written piece with the link https://dev.to/ulimicreator/to-pair-or-not-to-pair-introduction-1n9
Like many other processes, the implementation details of pair programming are left to the entity that intends to implement it. This is so because all effects are eventually carried and borne by the entity.
And whiles one can't properly quantify the productivity of programmers in a workplace, when done well, pair programming could provide these benefits:
Programmers get to learn easily from experienced developers and the knowledge flow is constant and all-encompassing to all participants.
Better code writing, since the one typing the code, i.e. the driver, justifies their code as they type by explaining why they are writing it in such a manner, and a probable input from the navigator could produce a better option.
More communication between programmers in the workplace since programmers who have been paired together would have been placed in the situation where they have to "program out loud" and express their opinions.
Programmers get to understand each other's workflow and habits, and this can serve as a fertile ground for
relationships.Real-time feedback on the programmer's code is received since with pair programming, the driver literally has someone "watching their back" and this eventually leads to less future code refactoring and reduces the chances of repeating smelly code.
Programmers tend to realize when paired with their fellow programmers that everyone makes mistakes, and understanding this fact is essential to a healthy mind.
Bonds are formed fast and relationships are established easily. This can be extremely beneficial to new employees. And whiles you don't need to be friends to work with someone, most of the boundaries that exist with acquaintances are removed and this produces more efficiency.
With pair programming, when new programmers are paired with programmers more familiar with the codebase they are initiated quite easily and efficiently.
Participants grow to be able to accept feedback and work on them fast, and being able to learn from your mistakes in due time makes you a better programmer and ultimately, a better human being.
Pair programming could be fun.
All suggestions and criticisms on any of my posts are accepted as long as they are not provided in a disparaging manner
Top comments (0)