XP is a Communist conspiracy.

-----Original Message-----
From: Cliff Rowley [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 16, 2002 2:01 PM

A bit of off-topic, but it's Friday, so there :)

Today I read an new article on IBM developerWorks on eXtreme
Programming, in which the author pretty much sorts the wheat from the
chaff in explaining XP, and I am very interested.  I'd avoided XP in the
past because all the FUD that surrounds it made it difficult for me to
determine exactly what it was and what it involved without spending a
significant amount of time researching it (time is money!).

Now I am curious as to who is using XP and how true it is to it's
promise of increased collaboration, increased productivity and more
importantly increased project success rate.

Being unedjumucated, I have found it difficult in the past dealing with
projects in the various ways I have experienced.  I've not had a great
time all in all, with too many horror stories for someone with only 4
years professional experience.  I've found myself asking 'why?' quite a
lot, and I've always wondered if there was a better way.  This also has
a lot to do with why I operate as a one man band, and generally try to
avoid 'complicated' development.

If anyone has any views on XP or any real world world experience with
it, I'd love to hear about it.  It appears that XP is being more widely
adopted these days, with JUnit and various other tools available that
support the XP processes.

The article is here, for anyone interested:
http://www-106.ibm.com/developerworks/library/j-xp0813/?n-j-8152
-- 

Regards

-------------------------------------------
 Cliff Rowley        |     [EMAIL PROTECTED]
 Software Engineer   |   www.doctype.co.uk
 +44 (0) 1206 514263 | www.cliffrowley.com
-------------------------------------------


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to