This message is from the T13 list server.
Glenn D: > I think we will someday start to see our English > departments teach courses on how to write for the > internet. They will be interesting. These have not already begun? > You have posted outside your cubicle an article on > Extreme Programming. Ive wanted to discuss this > with you for some time now. Sorry. > Are you a fan of this technique? I find it > intriguing. I find it intriguing. I don't have much experience of it. In my work of this moment, I am consciously trying to write nothing but what I know I need, and then live with the cost of change. > I especially like the test-as-you-go idea, as that > is the way I program, In Forth, yes. How about in C? > I wonder if formally written test suites are really > adequate. Non-trivial to make them so, I think. > No playing with the software? How do you do these > tests at the hardware/firmware interface? I'd like to see someone discuss how to use Extreme Programming with incompletely specified hardware ... I'm thinking that's a little bit like trying XP with an unreliable compiler. > The strong customer interaction is also great. Yes. > I think it works in well with your idea that the > only software documentation that makes sense > (besides a user manual) is the source code itself. Yes, that idea is a cost of change argument: almost nobody working for pay actually chooses to keep the comments up to date. > I, of course, automatically suspect any technique > that feels it must use a current buzzword (XP) to > promote itself, And I dislike the jargon collision with Win "XP". > and find some of the rules too inflexible, but I'm > wondering what your thoughts are. I'd like to meet & talk. > Have you had experience with it? No. > One warning sign--Ed Yourdon has come out in favor > of it--egad. Ouch. > ... Thanks for talking, Pat LaVarre
