I do believe that XP has it's place. I really think that it could dominate as a Open Source methodology. Having 5-10 developers and each reviews and can hop around and work on anything. What I find XP failing is that it cannot work with large teams that have specific talents for each individual developer. I like having DBA working on the DB, architects working on the architecture and the UI designers working on the UI. Now group reviews across these subgroups is great and needed. Any thoughts?
I also wanted to reply to your small issue remark. I also have this same philosophy. I like to call it the Onion development method. Get the "core" implemented/tested/working and then add "layers". After each layer do a full test cycle and verufy that the whole is working.
Like I said it was my initial reaction to the book. I do plan on reading it more fully. I have others respond as I have to the book and they have read it. Thanks for the reply.
I have flipped through this book at the bookstore and it looks to me as if they initiate a code then analyze/fix methodology. I have no problems with doing this on a project that has flexablity and no deadline. I do have a problem with the idea that you can skip the analysis and design stages of a large complex implementation and just code then go back and fix issues as they come up. Bad habits == bad results. A little planning goes a long way. I have great experience with past projects on this matter. But like I said I only have flipped through the book. Now I have to go buy it and really understand.
Remember that at the end of the year the amount and quality of news is significantly less that any time during the rest of the calendar year. That is why there are so many "scary" Y2K stories and now Cracker/Hacker stories. The News departments know that most people that continue to watch these news/entertainment prime-time programs are middle-class 35-60 Americans w/kids that don't understand the Internet and if they do they think it starts with "You've got mail!!". It is sad when journalist enlist attention starved individuals (so called Crackers) to make a segment of productive, hard working people (Hackers but I hate that word) look bad.
I am a Delphi developer and keep an eye on the discussions in the Inprise (Borland) newsgroups. Inprise technical employees are saying that this will not impead their development of Linux development tools. They have Interbase for Linux and are working on a JBuilder for Linux along with a few more Linux projects. I don't think that M$ will be forcing anyone at Inprise as long as the DOJ has them under the microscope.
Slashdot Mirror
I do believe that XP has it's place. I really think that it could dominate as a Open Source methodology. Having 5-10 developers and each reviews and can hop around and work on anything. What I find XP failing is that it cannot work with large teams that have specific talents for each individual developer. I like having DBA working on the DB, architects working on the architecture and the UI designers working on the UI. Now group reviews across these subgroups is great and needed. Any thoughts?
I also wanted to reply to your small issue remark. I also have this same philosophy. I like to call it the Onion development method. Get the "core" implemented/tested/working and then add "layers". After each layer do a full test cycle and verufy that the whole is working.
Like I said it was my initial reaction to the book. I do plan on reading it more fully. I have others respond as I have to the book and they have read it. Thanks for the reply.
If you started 12 weeks ago then how could you have 6 months of experience with XP?
I have flipped through this book at the bookstore and it looks to me as if they initiate a code then analyze/fix methodology. I have no problems with doing this on a project that has flexablity and no deadline. I do have a problem with the idea that you can skip the analysis and design stages of a large complex implementation and just code then go back and fix issues as they come up. Bad habits == bad results. A little planning goes a long way. I have great experience with past projects on this matter. But like I said I only have flipped through the book. Now I have to go buy it and really understand.
Remember that at the end of the year the amount and quality of news is significantly less that any time during the rest of the calendar year. That is why there are so many "scary" Y2K stories and now Cracker/Hacker stories. The News departments know that most people that continue to watch these news/entertainment prime-time programs are middle-class 35-60 Americans w/kids that don't understand the Internet and if they do they think it starts with "You've got mail!!". It is sad when journalist enlist attention starved individuals (so called Crackers) to make a segment of productive, hard working people (Hackers but I hate that word) look bad.
I am a Delphi developer and keep an eye on the discussions in the Inprise (Borland) newsgroups. Inprise technical employees are saying that this will not impead their development of Linux development tools. They have Interbase for Linux and are working on a JBuilder for Linux along with a few more Linux projects. I don't think that M$ will be forcing anyone at Inprise as long as the DOJ has them under the microscope.