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

    隨筆檔案

    文章分類

    文章檔案

    新聞分類

    新聞檔案

    相冊

    收藏夾

    搜索

    •  

    最新評論

    閱讀排行榜

    評論排行榜

    主站蜘蛛池模板: eeuss免费影院| 在线a免费观看最新网站| 亚洲国产日韩在线视频| 无码日韩精品一区二区三区免费 | 在线看无码的免费网站| 亚洲中文字幕无码中文| 国产亚洲精品无码拍拍拍色欲| 亚洲电影免费在线观看| 亚洲AV无码一区二区三区久久精品| 久久亚洲国产精品五月天婷| 国产成人精品免费视| 香蕉视频免费在线播放| 久久久久亚洲AV成人片| 亚洲美女高清一区二区三区| 蜜臀98精品国产免费观看| 一进一出60分钟免费视频| 亚洲成人免费网站| 久久久久噜噜噜亚洲熟女综合 | 亚洲va在线va天堂va不卡下载| 成年在线网站免费观看无广告| 男人天堂免费视频| 久久精品国产亚洲AV| 亚洲国产成人无码av在线播放| 亚洲色欲久久久久综合网| 无码一区二区三区免费视频 | 亚洲伊人久久综合影院| 成人无码区免费A片视频WWW| 你懂得的在线观看免费视频| 亚洲AV成人无码久久WWW| 亚洲欧洲日产国码www| 亚洲精品~无码抽插| 免费观看国产小粉嫩喷水| 午夜国产精品免费观看| 华人在线精品免费观看| 色多多www视频在线观看免费| 亚洲免费在线视频观看| 亚洲AV色香蕉一区二区| 亚洲综合色婷婷七月丁香| 国产女高清在线看免费观看 | 亚洲国产精品无码专区影院| 国产精品va无码免费麻豆|