<rt id="bn8ez"></rt>
<label id="bn8ez"></label>

  • <span id="bn8ez"></span>

    <label id="bn8ez"><meter id="bn8ez"></meter></label>

    jojo's blog--快樂憂傷都與你同在
    為夢想而來,為自由而生。 性情若水,風起水興,風息水止,故時而激蕩,時又清平……
    posts - 11,  comments - 30,  trackbacks - 0
    Let's change the email subject so Tim can stop scramming on us. :)

    Interesting point that Bill pointed out is the availability of the resource. I would like to have a discussion on it. As the whole idea of pair programming is to raise the overall team productivity , so the correct statement should be as follow:

    "Solo programming is bad so i don't want too. And we also need to think about the availability of the resource as the productivity of solo programming is really low."


    The reason that people always think pair programming is a waste, because:
    You are putting two developer to do a task that can be done by one developer.
         1. However, this is totally an illustration , you will realize the truth situation when you dig deeper:
    Solo , there are often situation that you are fooled by a simple typo , and spending few days to find it. You may finally solve it yourself, or your bored colleagues come to have a chat with you, look at your screen, and scrum out "You got a typo"...........   The later case is an example of power in pair programming ,i.e., navigating and discover what you overlooked.
         1. Solo, you may fall in sleep, low/no productivity.  Pair , your partner will not let's you.
         2. Solo, you play with msn and email . Pair, two developers won't get the chance.
         3. Solo, it's easily that you are moved from development to research, not doing the real thing. Pair, someone will warn you and drag you back.
         4. Solo, you can't think of a solution, not coz you are not good, but you are just not there. Pair, two brains always have a more complete solution.
         5. Solo, you learn something new yourself, wasting 4 days to pick up someone can teach you in an hour. Pair, both got trained and improved all the time.
         6. Of course, it's also correct that we should not drag everyone to pair programming at start for various reason, starting with a small groups of  interested developers is much better.


    F.Y.I. , I got 11 developers signed up about tonight event.

    And please click a confirm on facebook if you can.
    http://www.facebook.com/event.php?eid=8836123613Let's change the email subject so Tim can stop scramming on us. :)

    Interesting point that Bill pointed out is the availability of the resource. I would like to have a discussion on it. As the whole idea of pair programming is to raise the overall team productivity , so the correct statement should be as follow:

    "Solo programming is bad so i don't want too. And we also need to think about the availability of the resource as the productivity of solo programming is really low."


    The reason that people always think pair programming is a waste, because:
    You are putting two developer to do a task that can be done by one developer.
         1. However, this is totally an illustration , you will realize the truth situation when you dig deeper:
    Solo , there are often situation that you are fooled by a simple typo , and spending few days to find it. You may finally solve it yourself, or your bored colleagues come to have a chat with you, look at your screen, and scrum out "You got a typo"...........   The later case is an example of power in pair programming ,i.e., navigating and discover what you overlooked.
         1. Solo, you may fall in sleep, low/no productivity.  Pair , your partner will not let's you.
         2. Solo, you play with msn and email . Pair, two developers won't get the chance.
         3. Solo, it's easily that you are moved from development to research, not doing the real thing. Pair, someone will warn you and drag you back.
         4. Solo, you can't think of a solution, not coz you are not good, but you are just not there. Pair, two brains always have a more complete solution.
         5. Solo, you learn something new yourself, wasting 4 days to pick up someone can teach you in an hour. Pair, both got trained and improved all the time.
         6. Of course, it's also correct that we should not drag everyone to pair programming at start for various reason, starting with a small groups of  interested developers is much better.


    F.Y.I. , I got 11 developers signed up about tonight event.

    And please click a confirm on facebook if you can.
    http://www.facebook.com/event.php?eid=8836123613
    posted on 2009-04-17 16:45 Blog of JoJo 閱讀(142) 評論(0)  編輯  收藏 所屬分類: Linux 技術相關

    <2025年5月>
    27282930123
    45678910
    11121314151617
    18192021222324
    25262728293031
    1234567

    常用鏈接

    留言簿(6)

    隨筆檔案

    文章分類

    文章檔案

    新聞分類

    新聞檔案

    相冊

    收藏夾

    搜索

    •  

    最新評論

    閱讀排行榜

    評論排行榜

    主站蜘蛛池模板: 国产亚洲精品精品国产亚洲综合| 精品成在人线AV无码免费看 | 四虎永久免费观看| 亚洲小说区图片区| 精品国产sm捆绑最大网免费站| 亚洲综合在线成人一区| 成人福利免费视频| 亚洲人成网站日本片| 18禁成年无码免费网站无遮挡| 亚洲综合久久一本伊伊区| 毛片在线免费视频| 亚洲精品乱码久久久久久蜜桃图片| 天堂在线免费观看中文版| 亚洲av日韩综合一区久热| 国产又粗又猛又爽又黄的免费视频| 九九精品国产亚洲AV日韩| 免费午夜爽爽爽WWW视频十八禁| 美女被免费视频网站| 亚洲午夜久久久久妓女影院| 免费播放在线日本感人片| 午夜亚洲国产理论秋霞| 国产精品色拉拉免费看| 亚洲人成人伊人成综合网无码| 日韩在线天堂免费观看| yy一级毛片免费视频| 亚洲AV日韩AV永久无码下载| 97性无码区免费| 国产精品亚洲综合天堂夜夜| 亚洲狠狠婷婷综合久久久久| 曰批视频免费40分钟试看天天| 亚洲另类无码专区丝袜| 亚洲午夜福利717| 免费无码又黄又爽又刺激| 日本黄页网址在线看免费不卡 | 久久久久亚洲精品中文字幕 | 成年女人18级毛片毛片免费观看| 国产亚洲人成在线影院| 亚洲视频日韩视频| 亚洲国产精品成人| 3344永久在线观看视频免费首页 | 亚洲色丰满少妇高潮18p|