#+TITLE: KATA 001 for ToDo Backend (14/11/2016)

* Sitting one - going for shameless green.
The first commit of the kata is going for shameless green.
There has been no refactoring just getting the code to green based on
the results of tests.
The next stage should focus on the refactor cycle trying to improve
the code in discrete steps without ever breaking the tests.

** Tests timing
Using couchdb as the data base and everything on localhost tests are
completing in around 0.7s.

#+TITLE: KATA 001 for ToDo Backend (14/11/2016)

* Sitting one - going for shameless green.
The first commit of the kata is going for shameless green.
There has been no refactoring just getting the code to green based on
the results of tests.
The next stage should focus on the refactor cycle trying to improve
the code in discrete steps without ever breaking the tests.

** Tests timing
Using couchdb as the data base and everything on localhost tests are
completing in around 0.7s.

* Sitting Two
First refactor. The point of this refactoring was to move the`database
calls out of the main application and into its own file. The goal was
to completely implement the horizontal refactoring without being
distracted by other refactorings along the way. Where issues were
noticed then these were added by making TODO or FIXME notes.

At first blush I have made a new file of about 75 lines long and the
main file length has not changed. However I think overall the code is
cleaner and easier to reason about. Further the flocking rules in
abstracting out the code smells have made each router have a very
similar pattern. This should allow us to make further improvements in
future refactorings.

Add a retrospective of sitting twos refactoring.
Add a retrospective of sitting twos refactoring.
