Ken Orr 对 Java 程序员的建议 (写出高质量软件的秘密)

<iframe align="top" marginwidth="0" marginheight="0" src="http://www.zealware.com/csdnblog01.html" frameborder="0" width="728" scrolling="no" height="90"></iframe>

Ken Orr 对Java 程序员的建议 (写出高质量软件的秘密)http://weblogs.java.net/blog/johnreynolds/archive/2006/03/ken_orrs_advice_1.html

下面摘录部分:

John: "Ken... What advice would you give Java programmers?" 您对Java程序员有何建议

Ken Orr: "Don't define yourself as Java programmers." 不要把自己看成Java程序员

Being a good programmer really has very little to do with the languages that you know... Being a good programmer is mostly dependent on the methodologies that you know and on how you employ those methodologies.

做一个好的程序员和你使用何种语言没有关系.它依赖于你的方法学,以及如何应用这些方法学.

Good process design skills and good data modelling skills are the foundations for being a good programmer.

好的程序员需要过程设计技能和数据建模技能.

Model Driven Architecture is surely a form of CASE, but Ken feels that the focus isn't quite right.

模型驱动开发是CASE的一种形式.但Ken认为其关注的并不太正确.

UML was developed to meet the design needs of programmers. We need tools focussed on meeting the design needs of users.

UML是用来帮助程序员设计流程的需要的.我们需要工具来满足用户的设计需要.

If the granualarity of the services is too fine, then the process definition will probably have too many steps. SOA的粒度过细,过程定义将需要过多步骤.

If the granularity of the services is too coarse, then you won't be able to modify the process without modifying individual services. SOA粒度定义过粗,当需要修改流程的时候将不可避免的修改单独的服务

Master more than one design/programming paradigm. 掌握一种以上的设计/编程方法

No paradigm is perfect... that's why there are so many of them. 没有一种方法是完美的,所以才会存在很多不同得方法.

Trackback: http://tb.blog.csdn.net/TrackBack.aspx?PostId=630728