What practices do you use/have you tried?
-
Agile Programming? Extreme Programming? Aspect Oriented Software Development? It seems that these are all a lot of hot air theory and very little "here's an example of some code that was generated using these practices". And the cited case studies always seem so, well, contrived. Who really uses this stuff? Marc Help! I'm an AI running around in someone's f*cked up universe simulator.
Sensitivity and ethnic diversity means celebrating difference, not hiding from it. - Christian Graus
Every line of code is a liability - Taka Muraoka
Microsoft deliberately adds arbitrary layers of complexity to make it difficult to deliver Windows features on non-Windows platforms--Microsoft's "Halloween files"It all depends on what I'm coding, how much knowledge of the code I have already (maintenance), how much time do I have, knowledge of language, will I have to rewrite code in order to implement my code the right way?, etc... I don't use any named method that has a book written about it, I just code. Some days its more thought out than others. It's programming, not brain surgery. BW "I always wanted to be somebody, but now I realize I should have been more specific." - Lily Tomlin
-
Agile Programming? Extreme Programming? Aspect Oriented Software Development? It seems that these are all a lot of hot air theory and very little "here's an example of some code that was generated using these practices". And the cited case studies always seem so, well, contrived. Who really uses this stuff? Marc Help! I'm an AI running around in someone's f*cked up universe simulator.
Sensitivity and ethnic diversity means celebrating difference, not hiding from it. - Christian Graus
Every line of code is a liability - Taka Muraoka
Microsoft deliberately adds arbitrary layers of complexity to make it difficult to deliver Windows features on non-Windows platforms--Microsoft's "Halloween files"I never read any of these practices. But, when we were explaining our development procedure to another software firm, they referred to it as extreme programming. I don't care what the name is, whatever we are doing works. My article on a reference-counted smart pointer that supports polymorphic objects and raw pointers
-
I use the Get The Job Done methodology. Messy but it works. ;)
Paul Watson
Bluegrass
Cape Town, South AfricaMacbeth muttered: I am in blood / Stepped in so far, that should I wade no more, / Returning were as tedious as go o'er Shog9: Paul "The human happy pill" Watson
I've used that for 14+ years, never let me down yet :-) I've studied these various methodologies and just pick the best bits from them all but mainly I just go with what works at the time. Michael 'War is at best barbarism...Its glory is all moonshine. It is only those who have neither fired a shot nor heard the shrieks and groans of the wounded who cry aloud for blood, more vengeance, more desolation. War is hell.' - General William Sherman, 1879
-
It all depends on what I'm coding, how much knowledge of the code I have already (maintenance), how much time do I have, knowledge of language, will I have to rewrite code in order to implement my code the right way?, etc... I don't use any named method that has a book written about it, I just code. Some days its more thought out than others. It's programming, not brain surgery. BW "I always wanted to be somebody, but now I realize I should have been more specific." - Lily Tomlin
brianwelsch wrote: It's programming, not brain surgery. If you saw some of the code i need to maintain at times, you would seriously rethink your statement. :rolleyes: - Nitron
"Those that say a task is impossible shouldn't interrupt the ones who are doing it." - Chinese Proverb
-
Agile Programming? Extreme Programming? Aspect Oriented Software Development? It seems that these are all a lot of hot air theory and very little "here's an example of some code that was generated using these practices". And the cited case studies always seem so, well, contrived. Who really uses this stuff? Marc Help! I'm an AI running around in someone's f*cked up universe simulator.
Sensitivity and ethnic diversity means celebrating difference, not hiding from it. - Christian Graus
Every line of code is a liability - Taka Muraoka
Microsoft deliberately adds arbitrary layers of complexity to make it difficult to deliver Windows features on non-Windows platforms--Microsoft's "Halloween files"I think my answer is the same as that of most others. That is we use a blend of all methodologies based on our needs. I have often come across die hard believers of one methodology or another, but have found that based on circumstatnces, no one methodology works in every situation.
-
brianwelsch wrote: It's programming, not brain surgery. If you saw some of the code i need to maintain at times, you would seriously rethink your statement. :rolleyes: - Nitron
"Those that say a task is impossible shouldn't interrupt the ones who are doing it." - Chinese Proverb
Even with the assembly I have to go through, with poor to no comments mind you, its never more than patience and walking through step by step until you get what its doing. I guess I've found that that toughest part is always that don't know enough about the tools (ie. language, debugger, etc.). The tasks themselves are logical and predictable. Luckily, there is usually enough documentation somewhere on the tools to make it managable. (maybe i'm simplifying it too much) BW "I always wanted to be somebody, but now I realize I should have been more specific." - Lily Tomlin
-
Agile Programming? Extreme Programming? Aspect Oriented Software Development? It seems that these are all a lot of hot air theory and very little "here's an example of some code that was generated using these practices". And the cited case studies always seem so, well, contrived. Who really uses this stuff? Marc Help! I'm an AI running around in someone's f*cked up universe simulator.
Sensitivity and ethnic diversity means celebrating difference, not hiding from it. - Christian Graus
Every line of code is a liability - Taka Muraoka
Microsoft deliberately adds arbitrary layers of complexity to make it difficult to deliver Windows features on non-Windows platforms--Microsoft's "Halloween files"I know several managers that are found of DICOP: "Deadline Is Coming" Oriented Programming. It is a nice methodology, and has some unique characteristics that make it very useful: 1. Increased programmer productivity: when DIC, programmers will work in a speedy team effort, bringing up productivity. If you create several small and tight deadlines, you can keep your team on top-notch performance. 2. Feature pruning: all other methodologies create software that is bigger than you need. Who needs a “Save As” feature anyways? Can’t you simply use the OS file copy feature? When DIC, people will focus on the feature the user needs, not what he wants. 3. Tiered testing: with tiered testing, the work is divided in three tiers. The first tier, a.k.a., “development team testing”, or the “F5” testing form. They hit F5, and if it the code compiles and seems to run, a setup is built and sent to the second tier. The second tire is known as the “deployment testing”: if the setup runs ok, it is sent to the third tier. This tier is responsible for finding all the remaining bugs on the software, and is known as “customers”. 4. Increased programmer motivation: your team will become so motivated that they’ll come up early to work and only will go home late. They’ll be so motivated that you will notice some hygienic habits will be forgotten, so they can start working earlier in the morning. ,
It's not the fall that kills you: it's the sudden stop - Down by Law, Jim Jamursch (1986)
-
I know several managers that are found of DICOP: "Deadline Is Coming" Oriented Programming. It is a nice methodology, and has some unique characteristics that make it very useful: 1. Increased programmer productivity: when DIC, programmers will work in a speedy team effort, bringing up productivity. If you create several small and tight deadlines, you can keep your team on top-notch performance. 2. Feature pruning: all other methodologies create software that is bigger than you need. Who needs a “Save As” feature anyways? Can’t you simply use the OS file copy feature? When DIC, people will focus on the feature the user needs, not what he wants. 3. Tiered testing: with tiered testing, the work is divided in three tiers. The first tier, a.k.a., “development team testing”, or the “F5” testing form. They hit F5, and if it the code compiles and seems to run, a setup is built and sent to the second tier. The second tire is known as the “deployment testing”: if the setup runs ok, it is sent to the third tier. This tier is responsible for finding all the remaining bugs on the software, and is known as “customers”. 4. Increased programmer motivation: your team will become so motivated that they’ll come up early to work and only will go home late. They’ll be so motivated that you will notice some hygienic habits will be forgotten, so they can start working earlier in the morning. ,
It's not the fall that kills you: it's the sudden stop - Down by Law, Jim Jamursch (1986)
Daniel Turini wrote: "Deadline Is Coming" Oriented Programming :-D All you have to do is move everything to top priority and it will get done. BW "I always wanted to be somebody, but now I realize I should have been more specific." - Lily Tomlin
-
I use the Get The Job Done methodology. Messy but it works. ;)
Paul Watson
Bluegrass
Cape Town, South AfricaMacbeth muttered: I am in blood / Stepped in so far, that should I wade no more, / Returning were as tedious as go o'er Shog9: Paul "The human happy pill" Watson
Paul Watson wrote: I use the Get The Job Done methodology. As do I, although it does involve the occasional guerilla tactic. Sorry, couldn't resist... :-D Chistopher Duncan Author - The Career Programmer: Guerilla Tactics for an Imperfect World (Apress)
-
brianwelsch wrote: It's programming, not brain surgery. If you saw some of the code i need to maintain at times, you would seriously rethink your statement. :rolleyes: - Nitron
"Those that say a task is impossible shouldn't interrupt the ones who are doing it." - Chinese Proverb
I second that. I feel your pain. SOme of the code I maintain was written with famous BFI methodology (Brute Force and Ignorance). We actually tried modest entry into XP, and it seems promising, but only in some cases. I am actually huge Refactoring evangelist, and I saw that actually works, just I need to keep trying - it will get going eventually. SDK Maintenance Programmer