老印問題: 給老板寫了起草了這麽一封信

又是老印問題: 給老板寫了起草了這麽一封信, 大家幫看看

我們的開發團隊十來個人. 開發人員後台三個, GUI三個. GUI小組, 一個老印女在公司
資格老是lead developer, 我和另一個老美去年新加入的公司的, 半年多了, 也是senior, 但項目被她領導. 我們都歸一個管二三十人的美國人老板直接管.

這老印人還不錯,懂的也多, 就是項目質量太差, 程序裏漏洞百出. 因為一起工作, 她
又是lead, 我常常要我幫她fix bug, 非常頭痛. 我一直希望把每個人做的都分開, 因
為我的程序質量比她好太多了, bug非常少. 但她還是把我們三個人的任務混在一起,
大家互相改來改去, 害我背了不少黑鍋, 又不好跟大家說都是她的錯.

一個月前老板在會上看進度, 大發脾氣了一把. 其實都是她的bug, 大家以為是我們兩
的, 也許以為就是我的. 我在會上委婉得說了一下問題症結所在. 本來事後想找老板再
說說, 想想覺得沒意思, 就放棄了.

今天類似情況又發生了, 大家又以為是我們兩個人的責任. 可能還以為主要責任在我,
因為bug都是我fix的, 實際上都是她的寫的. 另外, 那老美今天會後立馬給幾個人發了信,表明幾個bug不是他的責任.

也不想把關係搞僵了, 在這公司我也就是等綠卡(2005 PD, 今年應該能拿到), 沒啥野
心. 給老板一人寫了這麽一封信, 大家看看如何?


I was thinking about talking to you after Phase I. I did not do that because
I thought as a team we should work out together instead of clarifying
responsibilities. So on phase II, my task were X and Y, but I spent more
time helping other developers fixing bugs. And for those 40 bugs(全大組的,
大半是GUI) still reported by QE, I took 17 of them. Only three of them are
really my phase II bug (two are requests to add colon or question mark in
text). Another three are either requirement clarification or historical
issues as you can see from the attached list.

I am not blaming anyone. XXX(老印女) still takes much more responsibilities
than B(老美) and me, so it is not fair to have her accountable for all bugs
from her code. ( That’s why I take the initiatives to fix the bugs. On the
other hand, I do not want to look bad in meeting because of the initiative.
). On client side, often two or even three developers are working on the
same page, and fixing each others’ bug. This approach helps in some ways,
but is not efficient and very easy to cause new bugs. For example, we three
are all working on the new XXX page. When developing new YYY feature, 80%
of my time was spent on fixing old bugs on this page.

The three developers on service side have well defined responsibilities(
might be one reason they have fewer bugs). Possibly we could gradually have
a more clearly defined responsibilities for client side as well without
sacrificing the flexibility and teamwork. Also, unless necessary, one
should avoid fixing other developers’ bug(it is too easy to create new bugs
when fixing others’ code).

Thanks for your consideration, please let me know if you have any questions
or want to meet!

所有跟帖： 

• TO BE HONEST, 覺得你說的有點兒亂啊。。。 -說實在的- ♀ (219 bytes) () 01/06/2009 postreply 14:48:09

• 這麽個說法，看行不~~ -LiYouCai- ♂ (426 bytes) () 01/06/2009 postreply 15:36:12

• 回複：老印問題: 給老板寫了起草了這麽一封信 -美國老垚- ♂ (102 bytes) () 01/06/2009 postreply 17:10:58

• 好人哪！大妹子（其實我也不知道你是不是男的），你啥 -娜土鷹金澳- ♂ (98 bytes) () 01/06/2009 postreply 17:19:07

• 我的建議是: -豬啊豬- ♀ (532 bytes) () 01/06/2009 postreply 18:35:47

• I agree with -noshit- ♂ (487 bytes) () 01/06/2009 postreply 20:00:45

• EMAIL的語氣太重,同意以上兩位的 -青李子- ♀ (292 bytes) () 01/07/2009 postreply 12:58:21

• Never complain in written -lisle- ♂ (573 bytes) () 01/07/2009 postreply 20:00:23

• Write it done to clear your mind, but -smileJJ- ♀ (92 bytes) () 01/08/2009 postreply 07:51:18