Those that you mention have honed their organizitional, problem recognition and design skills. The quality of their work product has little to do with technoloy. They are experievced and they continue to challenged themselves. They are artists and their best skills are conceptual skills. I would think it an impossibilty that employing an off the shelf framework system would somehow magically raise a developer to a par with those guys and gals.

It would seem dedication,paractice, focus with attention to detail are most important. A typical "commercial" framework hides the details and constrains the paradigm.

Better to just keep it all VFP. You get the full paradigm and you have access to detailed oriented developers that avoid working within the constraints of a "commercial" framework.


>Agreed. Developing your own framework is undoubtedly a rewarding learning experience, and I do not criticize those who do so. But I am not arrogant enough to think I could equal the work of some of the finest developers in our business (Rick Strahl, Drew Speedie, the Feltmans, etc.) -- work that has been battle hardened by thousands of users beating on it on a daily basis -- in any sort of cost effective way. No matter how low a value I put on my time, I can't justify trying to reproduce products that sell for a few hundred bucks. It would take me thousands of hours of work, if not more, and the end result wouldn't be as good. To me it wouldn't be a rational business decision to go that way.
>
>Mike
>
>
>>Terry, that is a very unfair and unrealistic comment. I only venture in here to set the message straight to any potential new VFP developers out there who may mistakenly understand your statement to mean that only unskilled developers would use a framework. I hope that was not the message you intended to convey...>