7 Replies - 1936 Views - Last Post: 03 October 2008 - 02:58 AM

#1 skyhawk133  Icon User is offline

  • Head DIC Head
  • member icon

Reputation: 1875
  • View blog
  • Posts: 20,284
  • Joined: 17-March 01

Extreme Programming (XP)

Posted 19 March 2007 - 02:00 PM

Extreme Programming seems to be the most popular agile process for software development. Do any of you use this or any other process when you develop??
Is This A Good Question/Topic? 0
  • +

Replies To: Extreme Programming (XP)

#2 Nova Dragoon  Icon User is offline

  • The Innocent Shall Suffer, Big Time
  • member icon

Reputation: 36
  • View blog
  • Posts: 6,169
  • Joined: 16-August 01

Re: Extreme Programming (XP)

Posted 19 March 2007 - 04:19 PM

EDIt:
Looks like theres been a new definition added to it. I remember it being much more limited when I first heard about it.
Was This Post Helpful? 0
  • +
  • -

#3 1lacca  Icon User is offline

  • code.rascal
  • member icon

Reputation: 44
  • View blog
  • Posts: 3,822
  • Joined: 11-August 05

Re: Extreme Programming (XP)

Posted 20 March 2007 - 01:38 AM

Haven't tried it yet.
And for those, who don't have a clue what's this all about.
Was This Post Helpful? 0
  • +
  • -

#4 ajwsurfer  Icon User is offline

  • D.I.C Regular
  • member icon

Reputation: 21
  • View blog
  • Posts: 373
  • Joined: 24-October 06

Re: Extreme Programming (XP)

Posted 20 March 2007 - 02:58 PM

I have a lot of bosses are pushing for Extreem Programming. However, when the rubber meets the road, and the project is really large, or there is little understanding, or defiinition, of the original problem, a fall back to traditional project management practices is a life saver.

I guess threading in peices to a large existing project doesn't need much planning, but it does requires a lot of experience with the original program before it can be done. Unfortunatly, most of the work that needs to be done is doing just this. And it usualy needs to be done on the spot, whether you have 10 years experience on the project or 10 minutes.

I would say I have had good results by using as many case tools as needed, to gain an understanding of the project, before diving in. Once a good understanding, and communication, about the project are reached, the process can be streamlined (even to a "Extreme").
Was This Post Helpful? 0
  • +
  • -

#5 ProfessorWC  Icon User is offline

  • New D.I.C Head

Reputation: 0
  • View blog
  • Posts: 21
  • Joined: 04-March 07

Re: Extreme Programming (XP)

Posted 21 March 2007 - 12:25 AM

I have actually never seen this programming style until now... being just a student though, I would probably try it to see how it works out.
Was This Post Helpful? 0
  • +
  • -

#6 NickDMax  Icon User is offline

  • Can grep dead trees!
  • member icon

Reputation: 2250
  • View blog
  • Posts: 9,245
  • Joined: 18-February 07

Re: Extreme Programming (XP)

Posted 24 March 2007 - 12:06 AM

Sometimes I am glad I am unemployed. This, like so many design systems, is about the most irritating thing I have seen. Lets take an example: paired programming - two coders working on the same computer. I would end up killing someone. Sounds to me like you will have one coder and one "sitting on my ass making smart comments so I can irritate this guy so he will get up off the keyboard and let me get to work." Most programmers I know may be good at playing well with others in a team environment, but get too close and they bite.

optomize last - God I hate this. Its like keeping your space clean in kitchen, yes it is easiest to do at the end of the night, but if you keep up with it as you go then the end of the night goes by with so much less hastle, and should the customer ever take a peek in the kitchen they will still eat there. It is not that you need to spend all you time trying to write the fastest code and worrying about clockcycles, but if you keep you eye on doing it right the first time, then when it comes time to optomize you are not saying, "well we could, but that would require rewrites here, here, and here, and that would push us past release data, and put us over budget... so we will just go with this crap."

It is not the spirit of the system that I disagree with. Large software projects really do require management (and "large" does not have to be all that big). The problem is that management philosophies are often based upon garbage fads. For example the "optomize last" craze that really misses the point.

Example: The last team project I was involved in was a fuzzy logic circuit design program. The project head wanted to write problem spacific code. I convinced him to take a more general aproach (I had the advantage as I would be coding the key components). The result was that when the customer went, "wow cool, can you make it do *this* too" we were able to turn the newer requirements arround in hours. Had we taken the original design pattern (which granted would have been faster in inital coding) we would have had to answer, "well, not as currently designed no." The project head later thanked me for saving his neck.

The mannager was not a bad programmer he was just caught up in what he thought was the best philosophy for the project: take the customer requirements and make each one a reality. I had a different aproach based upon many more years of experiance. He makes more money than I do. (yea, I am a little bitter sometimes).
Was This Post Helpful? 0
  • +
  • -

#7 salindor  Icon User is offline

  • D.I.C Regular
  • member icon

Reputation: 46
  • View blog
  • Posts: 301
  • Joined: 10-November 06

Re: Extreme Programming (XP)

Posted 24 March 2007 - 08:44 AM

View PostNickDMax, on 24 Mar, 2007 - 12:06 AM, said:

Sometimes I am glad I am unemployed. This, like so many design systems, is about the most irritating thing I have seen. Lets take an example: paired programming - two coders working on the same computer. I would end up killing someone. Sounds to me like you will have one coder and one "sitting on my ass making smart comments so I can irritate this guy so he will get up off the keyboard and let me get to work." Most programmers I know may be good at playing well with others in a team environment, but get too close and they bite.

optomize last - God I hate this. Its like keeping your space clean in kitchen, yes it is easiest to do at the end of the night, but if you keep up with it as you go then the end of the night goes by with so much less hastle, and should the customer ever take a peek in the kitchen they will still eat there. It is not that you need to spend all you time trying to write the fastest code and worrying about clockcycles, but if you keep you eye on doing it right the first time, then when it comes time to optomize you are not saying, "well we could, but that would require rewrites here, here, and here, and that would push us past release data, and put us over budget... so we will just go with this crap."

It is not the spirit of the system that I disagree with. Large software projects really do require management (and "large" does not have to be all that big). The problem is that management philosophies are often based upon garbage fads. For example the "optomize last" craze that really misses the point.

Example: The last team project I was involved in was a fuzzy logic circuit design program. The project head wanted to write problem spacific code. I convinced him to take a more general aproach (I had the advantage as I would be coding the key components). The result was that when the customer went, "wow cool, can you make it do *this* too" we were able to turn the newer requirements arround in hours. Had we taken the original design pattern (which granted would have been faster in inital coding) we would have had to answer, "well, not as currently designed no." The project head later thanked me for saving his neck.

The mannager was not a bad programmer he was just caught up in what he thought was the best philosophy for the project: take the customer requirements and make each one a reality. I had a different aproach based upon many more years of experiance. He makes more money than I do. (yea, I am a little bitter sometimes).


Don't get me wrong, it is possible to over optimize. For example, when I was taking a course on cryptography, we were required to work with a partner (or given the amount of work, and the deadline we were allowed towork with a partner). My partner was obsessed with optimization. The result was my code which did the job fast enough to meet all the teachers requirements and was easy to read was rewritten to be 'optimized', ya it ran 5% faster; but when it came to turn it it the 'optimized' code didn't work on the professors computer. Turns out he had optimized it for intel, cryix, windows, and red hat; but the professor was using madrake on an amd and what should not have been a problem (he swore up and down it should have worked) simply didn't.

The paired programming does sound incrediably annoying, I was under the impression it was two programmers sitting in the same room.
Was This Post Helpful? 0
  • +
  • -

#8 alfredjohn86  Icon User is offline

  • New D.I.C Head

Reputation: 0
  • View blog
  • Posts: 5
  • Joined: 29-September 08

Re: Extreme Programming (XP)

Posted 03 October 2008 - 02:58 AM

thank you
Was This Post Helpful? 0
  • +
  • -

Page 1 of 1