Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Amazon.com, Inc. (AMZN) -- Ignore unavailable to you. Want to Upgrade?

To: GST who wrote (158540)	7/14/2003 6:42:39 PM
From: Lizzie Tudor	Read Replies (1) \| Respond to of 164684

read a different book on extreme programming and you'll get a different definition of what it actually is. But my feeling is that it is basically a more generalized approach to what I have found to be extremely useful in software R&D. This is the notion that at least in enterprise software, most large issues/bugs are actually introduced in the integration phase and it is not reasonable to assume more design time will uncover these issues. The hardest R&D job I ever had, was a dotcom who was failing, we had to implement in 2 mos, do or die, and the R&D mgmt (me incl) said the approach was for all the developers to code something, unit test it once, and immediately put it into this integration test environment. People were walking over each other there but the big issues presented themselves immediately, just as expected, nobody thought of these things in design. This is the core of extr programming, and it works in my opinion. One issue is that you need an open work atmosphere where there isn't much finger pointing when somebody does something wrong. People have to feel ok about making mistakes and letting them become visible, as we all know some companies don't have the culture for that.