小组里水平第二菜的程序员决定了软件开发小组的质量（Eric）
2008-11-27 16:37
477 查看
source: http://www.artima.com/forums/flat.jsp?forum=106&thread=243273
Bad programmers can be far more productive in producing bad code than good programmers can be in cleaning up after them.
Programming "heroes" are people who provide business value by working in the core domain. Unfortunately, such "heroes" are often bad programmers who are smart enough to put themselves in the right place. Good programmers often have to clean up after them.
Instead of trying to rearchitect the whole system to begin providing business value in the third year (which never happens because you spend two years costing the company money while not providing any visible business value), you should situate yourself in the core domain. Create a facade to the underlying (bad) architecture and begin adding business value. Over time, you can change aspects of the underlying architecture when the benefits are clear.
Eric Evans
The quality of a software team is set to the second worst programmer on the team (everyone is carefully watching the worst programmer).Bad programmers can be far more productive in producing bad code than good programmers can be in cleaning up after them.
Programming "heroes" are people who provide business value by working in the core domain. Unfortunately, such "heroes" are often bad programmers who are smart enough to put themselves in the right place. Good programmers often have to clean up after them.
Instead of trying to rearchitect the whole system to begin providing business value in the third year (which never happens because you spend two years costing the company money while not providing any visible business value), you should situate yourself in the core domain. Create a facade to the underlying (bad) architecture and begin adding business value. Over time, you can change aspects of the underlying architecture when the benefits are clear.
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- 为何编程水平决定软件质量
- 为何编程水平决定软件质量
- Java 建模： 子整体软件开发，第二部分
- 程序状态决定软件质量
- 敏捷软件开发第二部分（SRP：单一职责原则）
- 高效程序员的45个习惯读书 ——敏捷开发修炼之道笔记之态度决定一切
- 个人的android软件的开发经历！（本人水平较差，菜鸟级的。。。。。。）
- 谁在谋杀效率和质量 大型软件开发协作困局
- 软件开发周期----如何提高软件开发质量
- 程序员在他们的软件开发生涯中最常犯的7个错误
- 读林锐《软件工程思想》------讲述软件开发和做程序员的道理
- 10位程序员眼中的2007:寻找软件开发利器
- 软件开发周期----如何提高软件开发质量----论团队管理的非技术性因素（part 2）
- 《程序员》杂志社 2010SD软件开发2.0大会随笔
- 程序员带你十天快速入门Python,玩转电脑软件开发（一）
- 从一个程序员笑话看软件开发管理
- 软件开发人员的作战手册 - 让程序员活的久一点
- OSG工程师/OSG程序员/c++程序员/OSG三维视景软件开发员/OSG软件开发工程师
- 软件开发质量管理层次模型
- 程序员必备的11个辅助开发的软件神器