Framing Software Reuse

The philosophy behind frames and framing techniques astonishes me. It is revolutionary and practical. I like it very much.Chancellor C.http://www.extremephonecards.com

I have pretty much experience with object oriented and procedural programming in several languages, now getting into AOP and byte code engineering. The first 30 minutes with this book were dissapointing - i couldn't figure out what the heck this guy is talking about. So i started at the front, not back cover. And this is my hint - read it from the beginning, page by page. I knew, there is something wrong with software development in general, now i know what it is exactly, and why. I knew it! More - i know how i can break this vicious circle and burn the tires. We've been going the wrong way folks! This definitely is the most valuable book in my monster library (some 100 titles). This is the top secret knowledge, worth thousands and thousands of bucks. I really am not related to the author or publisher. Great stuff!

Found my first copy in the university book store in Ames, Iowa, and have been looking at it constantly, until I lost it in one of my numerous moves. Bassett has the right idea. Software should be **engineered**, not hand crafted, and Netron seems to have found at least one way to do it. Another thing. To my knowledge, no one else in the field has advocated the notion of **balance** between source level changes and the re-use of executeable objects. This is probably the most important idea expressed here.

I thought I was becoming comfortable with OO until I ran into a group of Smalltalkers. What a mind bender! I learned things about OO that I didn't know. I also became concerned as, ostensibly for reuse purposes, the design stage decoupled logically unrelated functionality and fragmented real-world objects far beyond their natural granularity, to the point that I found myself mired in bitty components and methods with so little responsibility that I could no longer see the big picture. Worse, those myriad components now had complex interrelationships, most of which I could no longer see. I fully agreed that reuse was a worthy goal - but at the expense of readability and maintainability? Paul G. Bassett not only identifies and describes all of these issues (and much more), he has concrete solutions to these problems, with bottom line statistics to back up some pretty wild claims. His book is small - initially a concern for me. Don't worry. Paul G. Bassett is clear, concise, correct, complete. This, I strongly believe, is where we're headed.