[請益] 有公司用這種開發方式嗎?
最近聽朋友說他們公司在台灣與美國都有研發單位
同一個project,台灣與美國的RD同時在做
同一份code台灣RD在上班時間寫,等到下班的時候
剛好是美國上班時間,美國的RD繼續寫
也就是同一份code有兩個人同時在寫,也就是24hr都有人在寫
台灣還有其他公司用這種方式研發嗎?
這種方式看起來理論上是一天當兩天用,
應該可以縮短一半的開發時間
--
※ 發信站: 批踢踢實業坊(ptt.cc)
◆ From: 111.250.68.242
推
11/10 21:50, , 1F
11/10 21:50, 1F
→
11/10 21:51, , 2F
11/10 21:51, 2F
→
11/10 21:52, , 3F
11/10 21:52, 3F
→
11/10 21:52, , 4F
11/10 21:52, 4F
→
11/10 21:52, , 5F
11/10 21:52, 5F
→
11/10 21:53, , 6F
11/10 21:53, 6F
→
11/10 21:53, , 7F
11/10 21:53, 7F
→
11/10 21:53, , 8F
11/10 21:53, 8F
→
11/10 21:53, , 9F
11/10 21:53, 9F
→
11/10 21:53, , 10F
11/10 21:53, 10F
→
11/10 21:55, , 11F
11/10 21:55, 11F
推
11/10 21:55, , 12F
11/10 21:55, 12F
→
11/10 21:56, , 13F
11/10 21:56, 13F
→
11/10 21:58, , 14F
11/10 21:58, 14F
→
11/10 21:58, , 15F
11/10 21:58, 15F
推
11/10 21:59, , 16F
11/10 21:59, 16F
→
11/10 22:00, , 17F
11/10 22:00, 17F
推
11/10 22:12, , 18F
11/10 22:12, 18F
推
11/10 22:12, , 19F
11/10 22:12, 19F
→
11/10 22:13, , 20F
11/10 22:13, 20F
推
11/10 22:16, , 21F
11/10 22:16, 21F
→
11/10 22:17, , 22F
11/10 22:17, 22F
→
11/10 22:17, , 23F
11/10 22:17, 23F
→
11/10 22:17, , 24F
11/10 22:17, 24F
→
11/10 22:17, , 25F
11/10 22:17, 25F
→
11/10 22:18, , 26F
11/10 22:18, 26F
→
11/10 22:18, , 27F
11/10 22:18, 27F
補充一下,據朋友說,他們公司都是很有經驗的RD
基本上只要spec寫得很清楚,其實大家寫出來的東西都差不多
也就是無論給誰寫,大家想到implement的方式都不會差異太大
這算是『英雄所見略同嗎?』
※ 編輯: oomusou 來自: 111.250.68.242 (11/10 22:54)
→
11/10 22:53, , 28F
11/10 22:53, 28F
→
11/10 22:54, , 29F
11/10 22:54, 29F
推
11/10 23:01, , 30F
11/10 23:01, 30F
→
11/10 23:09, , 31F
11/10 23:09, 31F
推
11/10 23:19, , 32F
11/10 23:19, 32F
→
11/10 23:23, , 33F
11/10 23:23, 33F
→
11/10 23:23, , 34F
11/10 23:23, 34F
推
11/10 23:32, , 35F
11/10 23:32, 35F
推
11/10 23:37, , 36F
11/10 23:37, 36F
推
11/10 23:47, , 37F
11/10 23:47, 37F
→
11/10 23:48, , 38F
11/10 23:48, 38F
→
11/10 23:49, , 39F
11/10 23:49, 39F
→
11/10 23:54, , 40F
11/10 23:54, 40F
→
11/10 23:54, , 41F
11/10 23:54, 41F
→
11/10 23:56, , 42F
11/10 23:56, 42F
→
11/10 23:56, , 43F
11/10 23:56, 43F
→
11/10 23:57, , 44F
11/10 23:57, 44F
→
11/10 23:57, , 45F
11/10 23:57, 45F
→
11/10 23:58, , 46F
11/10 23:58, 46F
推
11/11 00:06, , 47F
11/11 00:06, 47F
推
11/11 00:07, , 48F
11/11 00:07, 48F
→
11/11 00:07, , 49F
11/11 00:07, 49F
→
11/11 00:09, , 50F
11/11 00:09, 50F
→
11/11 00:10, , 51F
11/11 00:10, 51F
→
11/11 00:11, , 52F
11/11 00:11, 52F
→
11/11 00:12, , 53F
11/11 00:12, 53F
→
11/11 00:13, , 54F
11/11 00:13, 54F
→
11/11 00:14, , 55F
11/11 00:14, 55F
→
11/11 00:14, , 56F
11/11 00:14, 56F
→
11/11 00:15, , 57F
11/11 00:15, 57F
→
11/11 00:16, , 58F
11/11 00:16, 58F
→
11/11 00:18, , 59F
11/11 00:18, 59F
→
11/11 00:18, , 60F
11/11 00:18, 60F
→
11/11 00:18, , 61F
11/11 00:18, 61F
→
11/11 00:23, , 62F
11/11 00:23, 62F
→
11/11 00:23, , 63F
11/11 00:23, 63F
推
11/11 00:24, , 64F
11/11 00:24, 64F
→
11/11 00:28, , 65F
11/11 00:28, 65F
看了大家的討論,我仔細想想,這種開發方式好像有以下這些好處
1.由於當天在接別人code時,一定要review一下別人寫的code,所以趁機可以
做一次code review,也可以順便看看兩人對spec的認知與邏輯是否有差異,
可以提早發現一些bug
2.由於是兩個人同時寫一份code,也就是兩個人都對這份code與架構都有一定的了解
若一人突然離職或者請假,另外一個人還是可以馬上接手,對project的傷害會最小
3.公司透過這種方式讓member交互的開發同一份code,可以有效的讓整個公司的
coding style趨於統一,而不是只是嘴巴喊喊而已
這種方式雖然不是很正統的Agile pair programming,不過好像又有點那種味道...
※ 編輯: oomusou 來自: 111.250.68.242 (11/11 00:39)
推
11/11 00:34, , 66F
11/11 00:34, 66F
→
11/11 00:35, , 67F
11/11 00:35, 67F
→
11/11 00:36, , 68F
11/11 00:36, 68F
→
11/11 00:36, , 69F
11/11 00:36, 69F
→
11/11 00:37, , 70F
11/11 00:37, 70F
推
11/11 00:49, , 71F
11/11 00:49, 71F
→
11/11 10:19, , 72F
11/11 10:19, 72F
推
11/11 12:41, , 73F
11/11 12:41, 73F
推
11/11 14:05, , 74F
11/11 14:05, 74F
推
11/11 21:35, , 75F
11/11 21:35, 75F
→
11/11 21:36, , 76F
11/11 21:36, 76F
推
11/12 02:05, , 77F
11/12 02:05, 77F
→
11/12 02:06, , 78F
11/12 02:06, 78F
→
11/12 02:06, , 79F
11/12 02:06, 79F
→
11/12 15:39, , 80F
11/12 15:39, 80F
→
11/12 15:39, , 81F
11/12 15:39, 81F
推
11/14 02:40, , 82F
11/14 02:40, 82F
→
11/15 20:42, , 83F
11/15 20:42, 83F
→
11/21 02:17, , 84F
11/21 02:17, 84F
討論串 (同標題文章)