Your daily dose of Java and related technologies.
News, Releases, Reviews, Tutorials, Articles, Events, Contests, Comments, Code and much more.
This java weblog is maintained by Xyling Technologies, making life simpler.

Thursday, February 17, 2005

Extreme Programming - Its simple.

The word extreme used to scare me to learn what extreme programming would mean. I tried some google searches and read some articles. But I could not read them fully. It was still scary.

Thankfully, I came across this small piece of explanation by Troy Holmes. A perfect blend of simple words and explanation. Compared to 100s of pages of articles, I feel reading couple of lines here would certainly save time and give peace to your mind :)

Extreme Programming (XP) has been an accepted form of software development for about eight years now. Many of the concepts found in this lightweight method of development have been implemented into the software shops without even the awareness that they were XP techniques. XP takes many of its fundamentals from other iterative development methodologies, including RAD and JAD.

[Resource-Type: Article; Category: Software Engineering/Extreme Programming; XRating: 5]
Title of the post takes you to the article at JDJ.

2 Comments:

Anonymous Kerry Sanders said...

A few weeks ago, my supervisor came to me and a fellow co-worker and talked with us about using Paired Programming to work on a project that we are currently working on. At first, I was a little skeptical about it. Ever since, though, I have really come to enjoy the day-to-day interaction with another developer. We bounce ideas off each other all the time. Learning something new from someone every once in a while is good too.

3:09 AM

 
Anonymous Anonymous said...

I'm a newbie to your site, but I quite like and will continue visiting. That said, I wanted to speak to your thoughts on XP. I have mixed reviews. While I think it works well for small developments shops, I don't think it can replace solid and disciplined development practices that you'd find in more established outfits. To address Kerry Sanders, I HATE paired programming. One of my bosses suggested we work together (side by side) on the machine... it was basically an exercise in back-seat driving. A more effective way, for me, is to have your "pair" in the same area (cube), or connected via some messenging client, and to be able to continually bounce ideas off each other while doing your OWN coding. Peer code reviews are a great idea though.

4:47 PM

 

Post a Comment

<< Home