[2]Developers make many shortcuts， copy and paste code for similar functionality to please management and deliver first version fast. They
do quick progress at the beginning， but code eventually becomes Big Ball of Mud.
開發(fā)者會走捷徑，拷貝相似功能的代碼來趕進度，并且爭取盡快發(fā)行第一個版本。他們一開始進展迅速，但是代
碼終會變成大泥球(比喻系統(tǒng)結(jié)構(gòu)不清晰)。
     6.Faster is slower(欲速則不達).
When we feel smell of success we start advance at the full speed without much caution. However， the optimal rate of growth usually is much
slower than the fastest growth possible.
當(dāng)我們看到成功的曙光，我們會全力以赴，不再小心謹慎。然而，優(yōu)增長速率通常會比可能的快增長速率要慢得多。
     [1]Managers add many people to already successful project. The overall progress becomes slower， because of communication overhead
and loss of team coherence.
經(jīng)理們往往為已經(jīng)成功的項目增加很多人手，但總體進展會變慢，因為交流所用的花費增加，以及團隊成員之間
失去默契。
     [2]Developers quickly add new features to the system without proper refactoring and improving existing code. System becomes difficult
to understand and modify.
在沒有對代碼進行合理重構(gòu)及改善的情況下，開發(fā)者快速的為系統(tǒng)添加新的功能，會使系統(tǒng)變得難懂，而且難以修改。
     7.Cause and effect are not closely related in time and space(在時間和空間上，因果并不密切相關(guān)).
We are good at finding causes to our problems， even if they are just symptoms and far from real root causes.
我們善于為出現(xiàn)的困難尋找原因，即使這些原因很牽強，并且遠非是真正的根本原因。
     [1]Development team stops accepting requirement changes from customers to finish a system in time. Customers are unhappy with delivered
software.
為了按時完成系統(tǒng)，開發(fā)團隊不再接受來自客戶的需求改變。因此，客戶對發(fā)行的軟件不滿意。
     [2]After few incidents with a live system， management compel developers to get approval and write detailed technical specification before
implementing any change in the system. Developers lose motivation for any improvements in the system and start procrastinating.
實時系統(tǒng)歷經(jīng)坎坷之后，管理層迫使開發(fā)者同意，并且在給系統(tǒng)做出任何修改之前撰寫詳細的技術(shù)說明。結(jié)果開發(fā)者
失去了為系統(tǒng)做出任何改進的動力，并且開始拖延。
     8.Small changes can produce big results-but the areas of highest leverage are often the least obvious(微小的改變可以產(chǎn)生明顯的效果，但這種杠桿效應(yīng)大的地方往往也不明顯).
Most obvious grand solutions like changing company policy， vision or tag line often don’t work. Small ordinary， but consistent changes could
make a huge difference.
像改變公司政策、愿景或者廣告用語這樣顯而易見并且關(guān)系重大的解決方案往往不起作用。相反，小而普通，但持續(xù)的改
變卻會帶來大不相同的效果。

 [1]Developers have everyday interactions with customer and make most decisions. As a result， customer needs are well understood， decisions
are better and solutions are optimal.
開發(fā)者每天都與客戶進行交流，并且做出大部分決定。因此，能夠更好地理解客戶的需求、做出更好的決定并且給出優(yōu)
的解決方案。

 [2]Developers build automated unit tests for each function in the system. As a result， design is flexible， people are confident， the system is fully
tested after each change.
開發(fā)者為系統(tǒng)的每項功能設(shè)計自動化單元測試。因此，設(shè)計更靈活、人們更自信、系統(tǒng)在每此修改之后都能得到完全的測試。
     9.You can have your cake and eat it too – but not at once(魚與熊掌可以兼得，但不是同時兼得).
We often face rigid “either-or” choices. Sometimes they are not dilemmas if we change our perspective and rules of the system.
我們經(jīng)常會面對刻板的“非此即彼”選擇。如果我們改變一下自己的觀點及系統(tǒng)規(guī)則，這些選擇有時并不會使我們進退兩難。
     [1]Experience managers know that we cannot increase the number of features and reduce time and cost simultaneously. However， it could be
possible to achieve if we just improve flow of ideas， find right people and avoid over-engineering.
經(jīng)驗豐富的項目經(jīng)理知道增加系統(tǒng)特性的數(shù)量與削減時間和開支不可兼得。然而，如果我們完善一下想法、尋找合適的人
才并且避免過度開發(fā)，這也是可能做到的。

  [2]Developers believe that they should follow either Transaction Script or Domain Model architecture patterns. However high performance
solution in the complex domain can combine both for the best effect.
開發(fā)者認為他們應(yīng)該要么采用事務(wù)腳本，要么采用域模型體系架構(gòu)模式。然而，復(fù)合域中的高性能解決方案可以將兩者結(jié)合，
以得到佳性能。

  10. Dividing an elephant in half does not produce two small elephants(把一頭大象分兩半不會得到兩頭大象).
Inability to see the system as a whole could often lead to suboptimal decisions.
無法整體了解系統(tǒng)，往往會做出次優(yōu)決定。