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

    隨筆檔案

    文章分類

    文章檔案

    新聞分類

    新聞檔案

    相冊

    收藏夾

    搜索

    •  

    最新評論

    閱讀排行榜

    評論排行榜

    主站蜘蛛池模板: 亚洲二区在线视频| 亚洲国产精品综合久久2007| 亚洲AV无码之国产精品| 在线免费观看中文字幕| 亚洲精品国产摄像头| 亚洲成AⅤ人影院在线观看| 深夜福利在线免费观看| 亚洲人成色77777在线观看大| 美女视频黄频a免费| 亚洲午夜无码片在线观看影院猛 | 亚洲成a人片77777kkkk| a级毛片在线免费| 亚洲男人天堂2017| 最近的中文字幕大全免费版| 久久综合亚洲色hezyo| 亚洲男人第一无码aⅴ网站| 你好老叔电影观看免费| 亚洲最大视频网站| 在线不卡免费视频| 一级做a爰片久久免费| 亚洲AV日韩精品久久久久久| 麻豆最新国产剧情AV原创免费 | 人妻仑刮八A级毛片免费看| 国产精品亚洲不卡一区二区三区| 最近免费mv在线观看动漫 | 免费一级全黄少妇性色生活片| 久久亚洲欧洲国产综合| 18禁美女裸体免费网站| 精品亚洲成a人在线观看| 国产亚洲精品a在线观看app| 嫖丰满老熟妇AAAA片免费看| 国产亚洲综合精品一区二区三区| 日韩精品亚洲aⅴ在线影院| 亚洲精品视频免费看| 无码免费又爽又高潮喷水的视频 | 亚洲色偷偷色噜噜狠狠99 | 亚洲黄色免费电影| 免费欧洲美女牲交视频| 99re在线这里只有精品免费| 亚洲av日韩综合一区二区三区 | 亚洲AV综合色区无码另类小说 |