XP極限編程
Extreme Programming
As we have explored in several issues of eAD, the two most pressing issues in information technology today are:
正如我們在eAD的若干期中探究的那樣，當今信息技術中最迫切的兩個問題是:
How do we deliver functionality to business clients quickly?
如何能快速地向商業用戶交付功能？
How do we keep up with near-continuous change?
如何才能跟上近乎連續的變化?
Change is changing. Not only does the pace of change continue to accelerate, but, as the September issue of eAD pointed out, organizations are having to deal with different types of change -- disruptive change and punctuated equilibrium. Disruptive technologies, like personal computers in the early 1980s, impact an industry (in the case of PCs, several related industries), while a punctuated equilibrium - a massive intervention into an ecosystem or an economy -- impacts a very large number of species, or companies. The Internet, which has become the backbone for e-commerce and e-business, has disrupted a wide range of industries -- more a punctuated equilibrium than a disruption.
變化本身也在不斷地變化中。不僅僅是變化的速度在不斷地提高，而且，如eAD的10月中所指出的， 組織正在不得不應付各種類型的變化-- 劇變與不斷被打破的平衡。 產生劇變的技術，象在80年代早期的個人計算機，衝擊了一個工業(PC機以及若干相關的工業)而不時打斷的平衡--一個對生態系統或者對整個經濟產生巨大影響的介入--則 影響了無數的物種，或者說，公司。已經成爲電子商務支柱的Internet, 就已使大範圍的行業產生劇變--更多的是打斷的平衡而不僅僅是一次劇變。
When whole business models are changing, when time-to-market becomes the mantra of companies, when flexibility and interconnectedness are demanded from even the most staid organization, it is then that we must examine every aspect of how business is managed, customers are delighted, and products are developed.
當整個商業模式正在發生變化，當"時間意味着市場"正成爲公司的咒語，當適應性與互連性正在成爲甚至是最呆板的組織的需要的時候，我們將有必要檢查以下的每一個方面:商業是如何管理的，客戶爲什麼而感到高興，以及產品是如何開發的。
The Extreme Programming movement has been a subset of the object-oriented (OO) programming community for several years, but has recently attracted more attention, especially with the recent release of Kent Beck's new book Extreme Programming Explained: Embrace Change. Don't be put off by the somewhat "in-your- face" moniker of Extreme Programming (XP to practitioners). Although Beck doesn't claim that practices such as pair programming and incremental planning originated with XP, there are some very interesting, and I think important, concepts articulated by XP. There's a lot of talk today about change, but XP has some pretty good ideas about how to actually do it. Hence the subtitle, Embrace Change.
終極編程(Extreme Programming )運動成爲面向對象編程這個團體的一部分已經有數年了， 但是直到最近才引起了越來越多的注意，特別是最近Kent Beck的《終極編程 釋義:擁抱變化》(Extreme Programming Explained: Embrace Change)一書的出版。千萬不要因爲終極編程(業內人簡稱爲XP)這一稱呼而對它產生反感。 儘管Beck沒有說象配對編程(pair programming)，增量式計劃(incremental planning)之類的來源 於XP,但是仍然有一些非常有趣的，我認爲也是很重要的概念可以借用XP來表達。現有有許多關於變化的討論， 但是XP卻有許多如何實際去做的非常好的想法。也就是這個副標題:擁抱變化。
There is a tendency, particularly by rigorous methodologists, to dismiss anything less ponderous than the Capability Maturity Model (CMM) or maybe the International Organization for Standardization's standards, as hacking. The connotation: hacking promotes doing rather than thinking and therefore results in low quality. This is an easy way to dismiss practices that conflict with one's own assumptions about the world.
有一種趨勢，特別在那些嚴格的方法論者中，希望剔除那些與"能力 成熟度模型"(Capability Maturity Model CMM)或者是國際標準化組織的標準相比不那麼笨重的方法，比如象hacking.註釋: hacking推崇行動而不是思考從而導致了較低的質量。 剔除與某人關於這個世界的假設相沖突的實踐，這倒不失爲一種簡單的方法。
Looked at another way, XP may be a potential piece of a puzzle I've been writing about over the past 18 months. Turbulent times give rise to new problems that, in turn, give rise to new practices -- new practices that often fly in the face of conventional wisdom but survive because they are better adapted to the new reality. There are at least four practices I would assign to this category:
從另一個角度來看XP，它倒可能是一個難題的某個潛在的部分，這個一個我在過去18個月中一直都在寫的內容。混亂 的時期產生新的問題，而後者又導致了新的實踐--新的實踐公然違抗 傳統的知識，但卻得以倖存下來是因爲它們能更好地適應這個新的現實世界。至少有四種實踐方式我覺得是屬於這個範疇的:XP -- the focus of this issue of eADXP -- eAD本期的焦點Lean development -- discussed in the November 1998 issue of eAD輕量級的開發(Lean development)--已經在eAD 1998 11月中討論Crystal Light methods -- mentioned in the November 1999 issue of eAD and further discussed in this issue輕量級的Crystal方法(Crystal Light methods)--曾在eAD 1999年11月提到，在本期中將做進一步的討論Adaptive software development -- described in the August 1998 issue of eAD (then called Application Development Strategies -- ADS)自適應軟件開發(Adaptive software development)--在eAD1998年8月中描述過(當時叫做應用開發策略Application Development Strategies -- ADS)Although there are differences in each of these practices,
there are also similarities: they each describe variations from the conventional wisdom about how to approach software development. Whereas lean and adaptive development practices target strategic and project management, XP brings its differing world view to the realm of the developer and tester.
儘管這些實踐中存在着差異，但是它們中也有相似的地方:它們都描述了與傳統軟件開發不同的方法。 雖然輕量級的開發與自適應開發針對的是戰略與項目管理的，但是XP卻用不同的視角將開發方法帶入了程序員與測試員的領域。
Much of XP is derived from good practices that have been around for a long time. "None of the ideas in XP are new. Most are as old as programming," Beck offers to readers in the preface to his book. I might differ with Beck in one respect: although the practices XP uses aren't new, the conceptual foundation and how they are melded together greatly enhance these "older" practices. I think there are four critical ideas to take away from XP (in addition to a number of other good ideas):
XP中許多部分其實都來自於業已存在的那些優秀的開發實踐。"XP中沒有一個想法是全新的。大多數想法產生的時間實際上和編程一樣古老"Beck在他書中的前言中這樣說道。但是我在某一個方面考慮的也許與Beck有所不同： 儘管XP所用的實踐方式不是全新的，但是概念的建立以及它們如何融合在一起極大地增強了 這些"老"的實踐。我想(除了許多其它的好思想外，還)可以從XP中提煉出四個關鍵的思想:The cost of change變化的成本Refactoring重構Collaboration協作Simplicity簡單化But first, I discuss some XP basics: the dozen practices that define XP. 但是首先，我們來討論XP的基礎:那十二個用於XP的實踐方式。
