Reading through this book, I made it a point to put ear marks on pages that I think we can use to improve our tests in FA (and potentially Trumps). As I read through a lot of pages nearthe middle of the became ear marked. This includes suggestion that quick-fit tests should be run seprately(which can be done in the existing environment as FA tests were refactored 2 iterations ago, and thus reduceour waiting time from 6+15 minutes to just 7 minutes) as well as making them more customer centric and readablerather than be developer oriented. This ranged from page formatting to using Do Fixtures. Some idea from this book will be implemented in the next release of my project.

This is one of the books that I would like to keep close and refer to to remind myself to use betterways of writing Fit tests and to use this framework to its full potential as well as keep things simpler.

“97 Things an Architect Should Know” is an excellent book which reflects on experiences of people who have practiced agile as well as those that have been in IT for more than a decade (It has some (ex) Thoughtworkers, but interesting none from Conchango). It sheds valuble inside into the work of architect as well as reiterate some important points (e.g. software is evolved and not developed, commit-and-run is a crime, avoiding “good ideas” which can effect the project negatively quiet easily, etc…). I think it is a good quick read to reflect on ones experiences on different project and how other people went on to resolve those issues, and potential project smells which no longer feel something that need resolving. However, to keep the book concise it was kept in a point format, which makes it hard to remember most of the points as these come about from experience and retained rather than learned beforehand. Nevertheless, it could be used as a reference to see how we can improve ourselves and excel.