Run through the example. Every time you compile, save the code
you just changed.
Solution is uploaded including the build.xml Etienne and I used to do
the zipping. I hope that the steps between the zips are not too big.
I assume you can do the "interpolation". We did not zip when compile
was broken. The information about broken or runnig tests is included
in each zip with the JUnit TestResult.txt.
If you have to go through all the zips without a good diff tool, then
make sure to visit the lavatory beforehand and go and get enough
snacks for the night :-)
The solution is anything but perfect. Lots of stuff is missing.
Exchanges are not yet symmetrical. But - everything was done true
test-first, sometimes assert-first from the very start. No design
decisions were taken without having the code asking for it. One
reason to pair on this task, was not to leave the smallest margin for
cheating. Thanks Etienne.
Etienne and I agreed, that while programming we had the feeling of
having a conversation with the system. I have to mention that Etienne
did not agree with the sequence of steps we did. He would have
preferred not to switch between additions and multiplications. I
agree that from hindsight our sequence is suboptimal. Etienne totally
dislikes the way the exchange rate is handled. At least it was
introduced in tiny working steps.
The last state is where more tests could ask for the symmetry of
operations and the "immutable" property. We went around the Java
problems with "equals" so far. We are prepared to tackle it now.
The zipfile names reveal the time we needed for each step, including
discussion time. Concerning the time spent, we are not satisfied with
our performance. But it was fun.
Is the build.xml, what you were asking for?
I'm terribly frustrated. That's good. Either I'll learn how to
explain what
I do, or I'll learn a better way to do.
Leonhard Euler was known for being a really friendly person. He
explained all his concepts to a cobbler's apprentice boy. He did not
stop improving the explanation until this boy understood it.
[Harro Heuser, Lehrbuch der Analysis]
