Re: YAGNI's and Planning for Change
Posted: Jul 19, 2005 3:29 AM
This answer is not really worth replying to, but here goes:
> So again, you have other XP practices failing
No. I have a single entry in this debate and made no reference to failing XP practices.
> Address your real problems.
This is patronising. I'm addressing the problems raised in the article. My 'real' problems, such as they might be, are irrelevant.
> But I'm not hearing, "This is a bad
> thing to do, but happened to be the least worst thing for
> this particular situation, as far as we could figure it
> out." I'm hearing, "Break this practice, because of fear
> that this practice might make things harder in the
Inventing quotations and presenting them as if they are mine is a nonsensical way to make a debate.
> (Oh, and as for b), you don't need to understand the
> changes that well. Find someone who does have some idea,
> and rely on your tests.
If you don't understand the changes you're making, how do you tell if your tests are sufficient to cover your ignorance?
> Even if you do make other parts of
> the system weird, they'll still work, because of the
> tests, and at some point, if nobody understands it now,
> someone will go back, clean it up, and make it
> comprehensible. And probably integrate it much better with
> the rest of the system to boot.
This is quite a extraordinary statement. You development philosophy appears to be nothing more than getting code out of the door that passes some tests, with a blind hope that those tests will cover you, even if you don't understand what you are doing. Any problems that arise from your code will be someone elses.
> Or nobody will ever touch it again, in which case, who cares?)
Have you considered that if nobody touches your code, it isn't necessarily a vindication of what you have written.
> Summary: this breaking of the YAGNI rule seems to be
> driven by fear. Address the fear.
Again more patronising nonsense. Software development isn't some sort of exercise in macho chest thumping.
Questioning the premises of a software development style is not a symptom of fear but of open thinking. On the other hand, patronising and accusing those who question - of being driven by fear - is not.