Robin Houston wrote:
> Well it isn't English, but it's *almost* comprehensible...
Sounds a bit like dadadodo, only it makes more sense :)
I like the section "Keep the design as simple as possible":
"The design strategy implies starting with a simple design and continually
improving it. In fact, design elements that are more complicated than
absolutely necessary at the moment are delayes, even if only for a few
minutes. That means that you choose from among several possible solutions
the one that appears to be the simplest yet will satisfy the test. You
program only what you really need right now, not, what you may need later
on. You even go so far as to remove unnecessary flexibility from the code.
You prove that the current solution is too simple by writing a test case
which justifies a more complex design.
"Ulrich: OK. You want me simply to get the test running and to forget
everything else for the moment.
"Felix: Exactly. What would you do, if you only had to implement this one
test?
"Ulrich: Hah, that's really easy.
public class Customer {
public void rentMovie (int daysRented) {
}
public int getTotalCharge () {
return 2;
}
}
"Felix: How extreme! But good..."
Extreme indeed... but it *does* satisfy the test cases they've written so
far, and it contains no unnecessary flexibility ;)
> *** TRANSLATION ENDS HERE ***
>
> Thanks, babelfish.
Well, copy and paste the next part of the page into babelfish.
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
All opinions are my own, not my employer's.
If you're not part of the solution, you're part of the precipitate.
