Re: violation. TDD isn't an absolute like XP. TDD is awareness of
the gap
between decision and feedback, and control over that gap. I could
have only
acceptance tests and be doing TDD. The gap would be large--days--
but for
extremely skilled programmers that might be enough.
This sentences were very valuable to me. I suggest to insert them
into the book.
Would you agree to the following?
Decision: use Value Object Pattern
Feedback: I have to do all that Java specific equals/hashcode stuff.
Decision: defer Value Object, observe code for when to introduce
Decision: start with type instead of type code
Feedback: introduction is not needed for quite some time
Re: superior. See previous post.
I agree. "Superior" makes no sense in this context, for there is no
absolute metric.
Let me put it like this:
The conversation with my code has less timespans of misunderstandings
when asking it for Dollars compared with asking it for Money("USD").
This may be because my language is different from yours.
cheers
Mittie
