Week 2 - OCD
It's been another good week for progress. The tiny green dots that measure our progress are much more numerous and our application now has an (extremely simple but functional) design, so we can begin banging on it like users rather than letting our automated tests have all the fun.
We seem to be able to knock out most of our planned activities by the middle of the week and our two major 'maths'-type programming problems have been solved. I'm pretty sure we're going to have the foundations and major user 'flows' of the site in place within a fortnight or so, leaving next month for a presentable design and lots of polishing.
It's hasn't been as plain sailing as the first week, we hit some real roadblocks on Tuesday as we battled manfully with the structure of our data in order to make sure the user's workflow on the site was as slick as possible. The pairing really helped. I think that on our own we'd both still have been stuck, but the continuous discussions that are part of this working style seem to loosen problems into solutions more readily.
I've found this week to be much more tiring. Whether this is to do with the lessened adrenalin of the second week or the effort that comes with the continual intensity of pair-programming I'm not sure.
An interesting observation this week was the different ways in which our programmers OCD makes itself apparent.
I like to operate in only very few files at a time, often closing loads of files when I take over the driving seat. Whereas Arun can often be found erasing trailing white space from the ends of lines and the bottom of files and lining stuff up in the code (he has apparently been drilled into this by working at wego with Chu Yeow).
Us developers are curious beings.
Weekly Stats 8 new features added with a current total of 76 scenarios. 652 lines of code and 1748 lines of test code with a code-to-test ratio of 1:2.7.
