隨筆檔案

The Architect (dedicated non-programming technical decision maker and problem solver for business):

架構師（專用非編程技術決策者，業務問題解決者）

1. Has outdated programming knowledge and experience, loss of touch with modern development approaches and practices.                                                                                                                                                                                             過時的編程知識和經驗，對現代的軟件開發方式和實踐缺乏關注。   


2. Don’t program and don’t know much about evolving system internals, but makes key technical decisions. Often has completely irrelevant and unreal picture what is happening with the system.                                                                       不進行軟件開發，對系統內部知之甚少，但卻要做出關鍵的技術決策。對系統經常有完全無關和虛幻的映像（不太會翻譯這句）。


3. Tends to complex, premature and generic solutions when the system is still in infancy and nothing is clear. Applies latest modern buzzword technologies as SOA, MDA, SaaS, Software Factories, etc. which look so beautiful in technical magazines, conferences and CV, but cause unnecessary headache for developers.                                      當系統仍處于起始階段，都還不明晰的時候，常會做出復雜的，不成熟僅僅通用的決策。使用在技術雜志、技術大會和CV上看起來如此美妙的現代最新的口號，諸如SOA，MDA，SaaS，Software Factories等等，只是給開發人員帶來不必要的頭痛。


4. Plays role of the middleman introducing complexity in coordination and project responsibilities. Represents software team in interactions with business customers reducing communication value for the rest of the team and impacting idea flow.                                                                                                                                                                          以中間人的角色，引入復雜的協調和項目的責任。代表開發組與客戶進行交流，屏蔽了其他成員的發言權和開發思想上的交流。（翻譯時候意思懂了，但就是表達不出來）


5. Reduces quality of decisions, which become limited to one perspective; decision making starts lacking diversity, independence and decentralization, which are essential attributes of collective intelligence.                                          決定僅僅局限在某個角度 ，降低了決策的質量；最初的決定缺乏多樣性，獨立性和向下兼容，這些都是集體決策的本質。                      


6. Creates tension with developers who experience mismatch between grand design and reality. Often continues pushing design decisions until the system becomes overly complex, difficult to change and becomes completely unusable.                                                                                                                                                                                             在缺乏大型設計和實現經驗的開發者之間制造緊張氛圍。不斷的做出決定，系統變得過度復雜，難于改變，和應用。


7. Secures job and justifies high salary - becomes authoritative center for solving business problems without much input from the team.                                                                                                                                                                            有穩定的工作和高薪，成為解決業務問題的權威，但卻從未融入到團隊當中。


8. Causes loss of sense of ownership, motivation and accountability in developers by detaching them from the key architecture decisions.                                                                                                                                                                     把開發人員排除在關鍵架構決策之外，讓他們缺乏主動性和責任感。


9. Concentrates project knowledge and the big picture in one head, limiting (and sometimes preventing) complete understanding for others.                                                                                                                                                                 只精通工程知識和大局一面，對其他方面幾乎一無所知。


10. Contributes to creation of specialized IT verticals that hurt relations with the business.                                                     擅長在縱向專門的IT方面建立聯系，但同時卻切斷了業務上的關聯。