Ten Commandments of Lousy Pair ProgrammingVivek Ganesan
schedule 1 year agoSold Out!
Want to understand how NOT to do Pair programming? Attend this session to see some funny examples of the same.
Pair Programming is to programming in the same way as Object Oriented Programming is to... well.. eh.. programming! Any agile startup which does not encourage Pair programming is referred to as by "stone age" startups by developer groups. And, the fact is that these developer groups are not fringe groups.
While there are a lot of guides to tell a beginner how to do pair programming, it is very easy to get a wrong understanding of Pair Programming. This session helps you understand nuances of pair programming by telling how NOT to do it.
Audience will be presented situations (a comic strip, a code block, a conversation, etc) and will be asked to spot what is wrong with each of those situations.
The summary will present ten things(that the audience found out from situations) that are not to be done during Pair programming.
Pair Programming - Myth Busters!
“If a task takes 1 hour; it takes 2 hours in pair programming.”
“This fix is needed urgently; it is better done alone to save time.”
“It is good only for complicated tasks; there is no need to pair program on simple tasks.”
These are some of the statements you may be hearing around you from experienced developers to even managers. Sadly, there is lack of understanding of dynamics that make pair programming a key agile engineering practice. This, in turn, resulted in lack of its acceptance in teams adopting agile methodologies. Our mission is to dissect the myths around pair programming which brings continuous learning, productivity, quality, and the joy of collaboration to countless developers every day.