I have really been enjoying the book. Thanks!
I do have one question. I bought the paperback edition of the book and downloaded the code from the site. In the folder structure that houses the code you tend to use single word folder names. In some cases, it is fairly obvious which folders match up with which chapters. In others, however, it is not obvious at all and since the parent folders tend to all have the exact same internal structure with the project in different stages it can be difficult to figure out which code is for which chapter.
This is how I have matched things up so far:
introduction - 1 ourproject - 2 foundation - 3
beyond - 5 things - 6 forum - 7 forum.1 - 7 security - 8 bigger - 9 seek - 10 seek.1 - 10 icing - 11 deploy - 12 model - (Chapter 4 ??) model.1 - ? model.2 - 3 model.3 - ?
Could you direct me to where this mapping exists or fill in the blanks in my list?
Seems it would just be easier if the folders were named Chapter_1, etc. :-)