Extreme Programming and VC++
-
Just trying to keep an open mind here. I was wondering what the communities thoughts were on Extreme Programming (XP) and the use of VC++. I have my reservations about its efficiencies. To me it seem that all things are sacrificed for the need to be flexibile. XP leads to excessive refactoring of code IMO. Not the easiest thing to do in VC++ given that it is a manual operation (Anyone know of any intelligent refactoring tools for VC++?) Success stories, horror stories? What do you perseve to be its Pros and Cons? Any thoughts on the subject would be most appreciated. Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain)me think that XP has nothing to do with VC++ ... heck, you could even do XP in cobol ... XP should be started as soon as possible on a project, when the initial designs, specifications and architecture are done. XP is about sharing the knowledge between the participants.
Maximilien Lincourt Your Head A Splode - Strong Bad
-
Antony M Kancidrowski wrote: To me it seem that all things are sacrificed for the need to be flexibile Which things? I see dead pixels Yes, even I am blogging now!
My main concerns are with regards to efficiency! Given a well defined set of requirements XP is not necessarily the most efficient path. For instance, Given a large architectual change, why provision for potential release partway through the change (any one of the iterations) when there is no value to the customer. Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain) -
I think XP is a fad. There are some good ideas that will survive but the bulk of it won't. It made sense from the perspective of companies in the boom times, but doesn't make much sense any longer. VC++ is in it's final stages of life and will become the realm of maintenance programmers just as Cobol has in the not too distant future.
"A preoccupation with the next world pretty clearly signals an inability to cope credibly with this one."
John Cardinal wrote: VC++ is in it's final stages of life and will become the realm of maintenance programmers just as Cobol has in the not too distant future. LOL, people have been saying that for years! The fact is that I am still using it and maintaining code written in it. Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain) -
Could you elaborate on this!? Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain) -
We're experimenting with a form of XP (agile programming), modified to suit our needs. While we're still very much a waterfall model shop, trying to incorporate AP in our development process has brought some welcome benefits: sharing of knowledge, increased productivity, and better code (as a result of required design and code reviews). [edit] (Sorry, I guess my post doesn't have anything to VC.) [/edit] /ravi My new year's resolution: 2048 x 1536 Home | Articles | Freeware | Music ravib@ravib.com
Thanks for that. We have adopted a form of XP deemed Iterative Development. From what you say it appears to work. How have you measured the benefits? In particular the increased productivity? Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain) -
me think that XP has nothing to do with VC++ ... heck, you could even do XP in cobol ... XP should be started as soon as possible on a project, when the initial designs, specifications and architecture are done. XP is about sharing the knowledge between the participants.
Maximilien Lincourt Your Head A Splode - Strong Bad
I was not stating that XP and VC++ went hand in hand I was wanting views on XP with regards to using XP when writing VC++. Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain) -
Just trying to keep an open mind here. I was wondering what the communities thoughts were on Extreme Programming (XP) and the use of VC++. I have my reservations about its efficiencies. To me it seem that all things are sacrificed for the need to be flexibile. XP leads to excessive refactoring of code IMO. Not the easiest thing to do in VC++ given that it is a manual operation (Anyone know of any intelligent refactoring tools for VC++?) Success stories, horror stories? What do you perseve to be its Pros and Cons? Any thoughts on the subject would be most appreciated. Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain)I love XP coding. Until you've actually worked some place that really uses it heavily, you won't be able to realize how great it is. One of the greatest things about it is (if implemented correctly) the absolute absense of feature creep without the requisite time to do them. Everything is fairly granular, so when they come asking for another feature to put in, they have to be able to have the velocity to get it done.
-
I love XP coding. Until you've actually worked some place that really uses it heavily, you won't be able to realize how great it is. One of the greatest things about it is (if implemented correctly) the absolute absense of feature creep without the requisite time to do them. Everything is fairly granular, so when they come asking for another feature to put in, they have to be able to have the velocity to get it done.
Yes this indeed does seem to be one of the pros. Just for extra information recently my company was bought by a larger company. The new company policy is to use XP. So it will be used heavily. I can see it being very useful to be able to show what will happen to the planned iterations if a feature is slotted into a feature set. I guess the project managers job is made easier. Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain) -
Could you elaborate on this!? Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain) -
Superb, that just may be the clincher for me to install the latest 2005 Beta2 I have been putting it off until now. :D Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain)