ObXProgramming: All the extreme programming techniques in the world are irrelevant if the requirements for the project are not well-designed and set in stone.
Um, one of the main points behind XP is that the requirement will change and so it allows them to change. Customers can add/change/remove Stories on a whim. They can even reprioritize the stories. I agree that you have to have stories to develop. But if a customer wants to change the code they just write a new story, give it a priority, and give the card to the programmers.
--Angus
Peer review in a metting setting sucks. It is hard to critisize someone's boneheaded code without offending them and putting them on the defensive in a big meeting room. With pair programming you can say "But how about WE do it this way instead?"
Chris, this is NOT an attack on you. I see that you are just offering a way out of pairing for those that can't hack the social interaction.
--Angus
Actually, pair programming is kind of fun. You get to ride the bow wave of your partner's energy as you cut through the code. It does assume that your partner has some skill, but it doesn't have to be equal. It just has to be close. One of the things that is being accomplished in a pair with a less skilled member is bringing that partner's skill up while he helps you to remember the little nitty crap you might forget.
--Angus
Most of the people writing about XP point to the fact that a lot of the abstraction that is written into code isn't ever used and sometimes actually causes problem when the programmer needs to jump in the other direction. XP has you pay the cost of abstracting something the SECOND time you need to use a certain part of the code, not the first time. Just write the test and then get the code to work. If you see something that isn't useful REMOVE it.
XP assumes you have the ability to work yourself out of a corner in a simple design, have the power to change the code that is locking you in the corner, and have a need to get out of that corner.
--Angus
In pair programming the other guy isn't really just sitting there looking over your shoulder. He is helping to keep track of all the crap you shouldn't have to while you are coding. You are focused on the tactical view and he is taking a strategic view. He reminds you to write the tests. He helps with the process of continually designing something. He keeps an eye out for refactorings that might be needed while you are added that data file systax. He is also there to act as your conscience and get your butt off slashdot and back to the code.
--Angus
He is talking about innovations that: came out of left field, shook the world by its roots, gained acceptance and you can't live without it
All of the Bio-blah advances are really cool, but they have yet to get to the stage of "Can't live without it." Some people might claim the cell-phone but even Dick Tracy and Star Trek had these.
--Angus
1) This is a documented way to make money from Free software. (One of the documents from MIT/AI stated this)
2) Microsoft chares for the application in the beginning and their every 4 year updates. They also charge for the developers network updates.
3) You can still get the updates for free, you just have to pay to use thier service.
--Angus
I am trying to figure out why they are so hyper about standards. They are like pringles, you can't have just one. (look at optical disk device drivers, what a mess)
Slashdot Mirror
ObXProgramming: All the extreme programming techniques in the world are irrelevant if the requirements for the project are not well-designed and set in stone.
Um, one of the main points behind XP is that the requirement will change and so it allows them to change. Customers can add/change/remove Stories on a whim. They can even reprioritize the stories. I agree that you have to have stories to develop. But if a customer wants to change the code they just write a new story, give it a priority, and give the card to the programmers.
--Angus
Peer review in a metting setting sucks. It is hard to critisize someone's boneheaded code without offending them and putting them on the defensive in a big meeting room. With pair programming you can say "But how about WE do it this way instead?"
Chris, this is NOT an attack on you. I see that you are just offering a way out of pairing for those that can't hack the social interaction.
--Angus
Actually, pair programming is kind of fun. You get to ride the bow wave of your partner's energy as you cut through the code. It does assume that your partner has some skill, but it doesn't have to be equal. It just has to be close. One of the things that is being accomplished in a pair with a less skilled member is bringing that partner's skill up while he helps you to remember the little nitty crap you might forget.
--Angus
XP only has you regularly working 8 hours a day and then kicks your butt out of the building to have a life.
--Angus
Most of the people writing about XP point to the fact that a lot of the abstraction that is written into code isn't ever used and sometimes actually causes problem when the programmer needs to jump in the other direction. XP has you pay the cost of abstracting something the SECOND time you need to use a certain part of the code, not the first time. Just write the test and then get the code to work. If you see something that isn't useful REMOVE it.
XP assumes you have the ability to work yourself out of a corner in a simple design, have the power to change the code that is locking you in the corner, and have a need to get out of that corner.
--Angus
In pair programming the other guy isn't really just sitting there looking over your shoulder. He is helping to keep track of all the crap you shouldn't have to while you are coding. You are focused on the tactical view and he is taking a strategic view. He reminds you to write the tests. He helps with the process of continually designing something. He keeps an eye out for refactorings that might be needed while you are added that data file systax. He is also there to act as your conscience and get your butt off slashdot and back to the code. --Angus
He is talking about innovations that:
came out of left field, shook the world by its roots, gained acceptance and you can't live without it
All of the Bio-blah advances are really cool, but they have yet to get to the stage of "Can't live without it." Some people might claim the cell-phone but even Dick Tracy and Star Trek had these. --Angus
1) This is a documented way to make money from Free software. (One of the documents from MIT/AI stated this)
2) Microsoft chares for the application in the beginning and their every 4 year updates. They also charge for the developers network updates.
3) You can still get the updates for free, you just have to pay to use thier service. --Angus
I am trying to figure out why they are so hyper about standards. They are like pringles, you can't have just one. (look at optical disk device drivers, what a mess)