I liked it.
http://en.wikipedia.org/wiki/Pair_programming
"Pair programming is an agile software development technique in which two programmers work together at one workstation. One, the driver, writes code while the other, the observer or navigator, reviews each line of code as it is typed in. The two programmers switch roles frequently. "
I liked the concept but I am not sure it always help. I would prefer programming as small groups with 3 to 5 members. With good version control system and at least one expert in each team it will be very effective. Dividing the tasks for each in a quick group discussion will help to avoid duplication of work and improve knowledge of everyone.
I further read something interesting about pair programming by Joel in
http://www.joelonsoftware.com/articles/FiveWorlds.html
" Lo and behold, I discovered that very few of the bugs in there would have been discovered with pair programming or test driven development."
http://en.wikipedia.org/wiki/Pair_programming
"Pair programming is an agile software development technique in which two programmers work together at one workstation. One, the driver, writes code while the other, the observer or navigator, reviews each line of code as it is typed in. The two programmers switch roles frequently. "
I liked the concept but I am not sure it always help. I would prefer programming as small groups with 3 to 5 members. With good version control system and at least one expert in each team it will be very effective. Dividing the tasks for each in a quick group discussion will help to avoid duplication of work and improve knowledge of everyone.
I further read something interesting about pair programming by Joel in
http://www.joelonsoftware.com/articles/FiveWorlds.html
" Lo and behold, I discovered that very few of the bugs in there would have been discovered with pair programming or test driven development."
No comments:
Post a Comment