Comments on: Pair programming / animations http://aras-p.info/blog/2006/02/15/pair-programming-animations/ Random thoughts of a triangle pusher Thu, 09 Feb 2012 07:56:51 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: ReJ http://aras-p.info/blog/2006/02/15/pair-programming-animations/comment-page-1/#comment-122 ReJ Thu, 16 Feb 2006 15:40:00 +0000 http://aras-p.info/blog/?p=87#comment-122 Yeah, that was rather enlightening :) Yeah, that was rather enlightening :)

]]> By: NeARAZ http://aras-p.info/blog/2006/02/15/pair-programming-animations/comment-page-1/#comment-123 NeARAZ Thu, 16 Feb 2006 10:08:00 +0000 http://aras-p.info/blog/?p=87#comment-123 ReJ: of course, shadows from everything onto everything, with zero artifacts, handling all corner cases and running insanely fast on any hardware!<BR/><BR/>Was that helpful? :) ReJ: of course, shadows from everything onto everything, with zero artifacts, handling all corner cases and running insanely fast on any hardware!

Was that helpful? :)

]]> By: ReJ http://aras-p.info/blog/2006/02/15/pair-programming-animations/comment-page-1/#comment-124 ReJ Thu, 16 Feb 2006 09:03:00 +0000 http://aras-p.info/blog/?p=87#comment-124 > I went to do some research on shadows!<BR/><BR/>What is your target to achieve with shadows right now? If that is not a NDA of course :) > I went to do some research on shadows!

What is your target to achieve with shadows right now? If that is not a NDA of course :)

]]> By: blackpawn http://aras-p.info/blog/2006/02/15/pair-programming-animations/comment-page-1/#comment-125 blackpawn Wed, 15 Feb 2006 21:12:00 +0000 http://aras-p.info/blog/?p=87#comment-125 i had to do pair programming for a project in college. it did not work out well. i think an important part is for the pair to be peers - ie of similar skill/experience level.<BR/><BR/>at microsoft some of the benefits of pair programming are achieved by having code reviews for every checkin. this means you can go off and write a bunch of code at your own pace and then before you check in you get someone else on the team to go over it. in practice this was mostly a waste of time and the reviews didn't find too many bugs. instead it was lots of debating about equivalent ways of implementing things or trivial minutiae.<BR/><BR/>where i work now a much better system is used. you can check in code without needing a code review, but team leads take time to review the code that is checked in. so it's not every checkin, but more like every once in awhile or after an important change a lead goes through the changes carefully looking for errors. this plus a culture that encourages very efficient and clean code plus constant testing seems to work very well. i had to do pair programming for a project in college. it did not work out well. i think an important part is for the pair to be peers – ie of similar skill/experience level.

at microsoft some of the benefits of pair programming are achieved by having code reviews for every checkin. this means you can go off and write a bunch of code at your own pace and then before you check in you get someone else on the team to go over it. in practice this was mostly a waste of time and the reviews didn’t find too many bugs. instead it was lots of debating about equivalent ways of implementing things or trivial minutiae.

where i work now a much better system is used. you can check in code without needing a code review, but team leads take time to review the code that is checked in. so it’s not every checkin, but more like every once in awhile or after an important change a lead goes through the changes carefully looking for errors. this plus a culture that encourages very efficient and clean code plus constant testing seems to work very well.

]]> By: Ignas MikalajÅ«nas http://aras-p.info/blog/2006/02/15/pair-programming-animations/comment-page-1/#comment-126 Ignas MikalajÅ«nas Wed, 15 Feb 2006 13:58:00 +0000 http://aras-p.info/blog/?p=87#comment-126 In a day to day programming pair programming is more of a quality assurance method. Like an extreme peer review ;) Two programmers are not just less likely to do unintentional bugs, but they are way less likely to cut corners. Two programmers will "do the right thing" even if it takes more time, is more difficult or boring.<BR/><BR/>And of course like with all the quality assurance methods - you get some quality you lose some speed, it's a trade off. Works for me though ;) In a day to day programming pair programming is more of a quality assurance method. Like an extreme peer review ;) Two programmers are not just less likely to do unintentional bugs, but they are way less likely to cut corners. Two programmers will “do the right thing” even if it takes more time, is more difficult or boring.

And of course like with all the quality assurance methods – you get some quality you lose some speed, it’s a trade off. Works for me though ;)

]]>