<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)

    隨筆檔案

    文章分類

    文章檔案

    新聞分類

    新聞檔案

    相冊

    收藏夾

    搜索

    •  

    最新評論

    閱讀排行榜

    評論排行榜

    主站蜘蛛池模板: 欧美日韩亚洲精品| 亚洲色大成网站www永久网站| 免费人成动漫在线播放r18| 插B内射18免费视频| 亚洲午夜电影在线观看高清| 最近免费字幕中文大全视频| 亚洲春色在线视频| 小日子的在线观看免费| 久久精品国产亚洲AV无码麻豆| 任你躁在线精品免费| 亚洲国产精品VA在线观看麻豆| 日本免费一区二区久久人人澡| 亚洲av之男人的天堂网站| 日本免费久久久久久久网站| 亚洲酒色1314狠狠做| 成人福利免费视频| 亚洲欧美熟妇综合久久久久| 在线观看免费大黄网站| 另类专区另类专区亚洲| 亚洲人成网77777亚洲色| 最近免费中文字幕大全免费| 国产精品亚洲四区在线观看| 日本媚薬痉挛在线观看免费| 免费在线观看自拍性爱视频| 久久久久亚洲精品无码网址| 99精品一区二区免费视频| 亚洲午夜一区二区三区| 午夜毛片不卡高清免费| 日韩免费在线中文字幕| 亚洲国产精品线在线观看| 成人免费午夜在线观看| 国产福利免费视频| 亚洲精彩视频在线观看| 四虎永久在线精品视频免费观看| 中国精品一级毛片免费播放| 亚洲自偷自拍另类图片二区| 国产无遮挡吃胸膜奶免费看| 久久九九全国免费| 在线观看亚洲专区| 亚洲伊人tv综合网色| 在线观看91精品国产不卡免费|