Ken Orr 對 Java 程式設計師的建議 (寫出高質量軟體的祕密)

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