>
It could be useful if it helped one understand existing frameworks - what kind of stuff goes in them, styles of metadata, when and when not to subclass, or whatever, emphasizing the differences between frameworks.
>

If you want to understand an existing framework, I don't think there is a better resource than the docs for that framework. IMO, VFE is the best documented framework on the market...

>What books would you recommend?

You know, I am glad you asked that question. For the most part, I think techical books are crap. The prevailing quality is dismal. The material is either incomplete or it is untimely. The publishing process and a solid TQM (Total Quality Management) strategy are constantly at odds.

In addition, many, especially in this community, have over-complicated the OO analysis and design discipline. Why folks have to make things so complicated is beyond me. That is my rant of the year -

Why do developers - especially VFP developers - insist on leaving common sense behind. IMO, simple and easy to understand is best. Over complicated and esoteric-ness is useless.

With that in mind, I suggest Scott Ambler's books. He writes for Software Development monthly. His books are clear, concise, and easy to understand.

We have a community where many people have learned that it is OK to expend $15K worth of time in analysis and design in order to solve a $300 problem. And for the most part, those that continually throw the lingo around usually are at a loss for a clue as to how to really "do" this stuff.

My advice - keep it simple and use your common sense. Don't spend $15K to solve a $300 problem. Check out Ambler's books. You will like them...


But hey, what do I know???? I'm just a loudmouth!! < bg >...

< JVP >