Software Engineering discussion
Beautiful Code
>
Framework for Integrated Test
date
newest »
newest »
message 1:
by
[deleted user]
(new)
Jul 05, 2010 07:50PM
This chapter did cause me to reflect back upon hardened OO rules, why they exist, and when it might make sense to break them. The comments on the rigidity and complexity of most framework code are right on. I was not, however, totally sold that this test solution is more "beautiful" than a more traditionally-based design. Like many other chapters in this book, it would require deeper thought from me to be convinced.
reply
|
flag
I was really lost in this chapter. I didn't understand what they were trying to solve or advocate through most of the chapter.I liked section 6.4 regarding the Simple HTML parser. I spent extra time analyzing this section and started to understand what previous sections had been discussing.
By the end of the chapter, I started to comprehend what this chapter was about.
The description of the FIT testing framework is another example of Bentley's earlier chapter on "Beautiful Code I Never Wrote". The framework is sparse like a well written musical composition where every note is present for a purpose and there are no extraneous elements. The visual metaphor I see is a 3-D wire-frame box and the goal is to be able to reach every part of the space in the box in an efficient manner. So the trick is to create the minimal path(s) as a framework that will allow others to follow and extend off of those paths. The users can then reach anywhere in the 3-D space with minimum effort from the framework "roads".
Shift that 3-D metaphor from physical space to "Informational Space". A well crafted framework will allow its users to reach any point in that space with a minimal effort of extension from the framework.
It looks like FIT achieves that goal by its elegant design in its corner of 'information space'.
Looks like this is an opportunity to finally participate in the discussions. Hi Steph, Hi Brad. Hi Erik. I have been silently reading all the comments but have been unable to participate. Time to pitch in!
