Java开发网 - 有谁做过pair progamming的有事相求

Java开发网

您没有登录

» Java开发网 » Design Pattern & UML » Agile development

打印话题 寄给朋友 订阅主题

话题被移动

该话题已被移动 - why , 2004-05-17 11:09
如果您尚不清楚该话题被移动的原因，请参考论坛规则以及本版公告或者联系本版版主。

作者	Re:有谁做过pair progamming的有事相求 [Re:emarket]
emarket 亢龙有诲 CJSDN高级会员发贴: 460 积分: 82	于 2004-04-29 15:09 我一天用一半的时间写程序，一般的时间看东西，要是跟你结对编成，你老看着我，我没法做自己的事情了：）

作者

Re:有谁做过pair progamming的有事相求 [Re:emarket]

linux_china

版主

发贴: 752
积分: 240

于 2004-04-29 16:12

别人看你，那是你自己的感受。习惯就好啦！
一天用一半的时间编程，那你是幸福啦，结队编程应该每天工作在2/3左右。其余时间可自己处理，进行交谈，效果更好。正是像你这样，结队才能更好，动不动上上网，检查邮件，很难集中思维的，程序出错也难免的。如果真的要结队的话，有些学习的东西就得其他时间完成啦，然后共同交流，我认为效果更好。

作者

Re:有谁做过pair progamming的有事相求 [Re:linux_china]

floater

Java Jedi

总版主

发贴: 3233
积分: 421

于 2004-04-30 00:58

linux_china wrote:
跟同事商量一下，反对居多，认为浪费，还有心里因素吧！
中国人好像很不愿意合作！
建议看看Addison Wesley的Pair Programming Illuminated，启发不小！
只好自己大呼：我要结队编程！
培训教程： http://www4.ncsu.edu/~lawilli3/PP/tutorial.ppt

I found most of chinese who don't like this style has these problems:
1. not willing to do things better, just go with the flow.
2. afraid of making mistakes, 心里因素.
Once they benefit from pp, they are willing to do it. The benefit I see:
1. know a different way(probably better) to do things.
2. combined knowledge make things faster, everyone has his own tricks.
Remember, pp is not mentoring!

"Any fool can write code that a computer can understand. Good programmers write code that humans can understand."
- Martin Fowler, Refactoring - Improving the Design of Existing Code

作者

Re:有谁做过pair progamming的有事相求 [Re:emarket]

floater

Java Jedi

总版主

发贴: 3233
积分: 421

于 2004-04-30 01:03

emarket wrote:
我一天用一半的时间写程序，一般的时间看东西，要是跟你结对编成，你老看着我，我没法做自己的事情了：）

I am doing the half-half too. I believe it should be 1/3 coding, 2/3 r&d.

My most productive time is cigarette breaks, when new ideas come out, new messages are being passed around among colleagues.

"Any fool can write code that a computer can understand. Good programmers write code that humans can understand."
- Martin Fowler, Refactoring - Improving the Design of Existing Code

作者

Re:有谁做过pair progamming的有事相求 [Re:emarket]

zyzhang

Explorer

发贴: 155
积分: 30

于 2004-05-25 19:46

Some practices on pair programming:

I agree that pairing programming is a challenge when implementing in the real world. In my company, we only do pair programming when needed(can improve the productivity), one criteria is when the user story is complex and need the combination different skill strengthes from different developers.The first thing is making some little effort on design(drawn CRC cards,or UML sketch), and then quickly go into the coding activity, each developer works on the area he holds strong experience, and express some best practices he knows..., for trivial tickets(maping user story), we donot do pair programming. Currently ,This way works fine in my company.

XP is just some principles, and generally, need customization to fit in the process of specific company. XP is also unformal compared with RUP for complex projects.

.....

作者

Re:有谁做过pair progamming的有事相求 [Re:zyzhang]

emarket

亢龙有诲

CJSDN高级会员

发贴: 460
积分: 82

于 2004-05-25 21:46

pair programming得目的不是发挥各自的所长时才用， pair programming是为了ensure continues code review. 所以每一行都应该由两个人写。像技术得传染只是个副产品。

xp 是一种 agile development 方法，实现了agile宣言，强调交流，反馈，简单，勇气四个 value 。同时 xp又被具体的12 practice所表现。当然我们可以有
local adaption, 但是不能偏离的太远，“扬弃” 的做法也是不可取的。否则就不是XPl了。

zyzhang wrote:
Some practices on pair programming:

I agree that pairing programming is a challenge when implementing in the real world. In my company, we only do pair programming when needed(can improve the productivity), one criteria is when the user story is complex and need the combination different skill strengthes from different developers.The first thing is making some little effort on design(drawn CRC cards,or UML sketch), and then quickly go into the coding activity, each developer works on the area he holds strong experience, and express some best practices he knows..., for trivial tickets(maping user story), we donot do pair programming. Currently ,This way works fine in my company.

XP is just some principles, and generally, need customization to fit in the process of specific company. XP is also unformal compared with RUP for complex projects.

.....

已读帖子

新的帖子

被删除的帖子