20 Years ago when I first started programming, I was programming IBM mini computers. I was able to read the complete documentation of the programming language and operating system in a matter of days. Within a few months I felt like an expert and was able to create robust solutions for some very complex applications. The language and operating system were extremely reliable.

To day I am a Visual Foxpro developer. I use VFP as my example, but I am sure that what I have to say is true of any other major development language.

I have to devote more time than ever to learning VFP and all the associated tools (less billable time). I have been with FoxPro since the FoxBase days, yet I feel as though I know less of the product than I ever have, even though I have invested more time than ever learning.

I can not reliably use the product with out the addition of frameworks, database tool kits, file repair utilities and other add ins (increased expense). I am grateful to frameworks not only for helping to reduce complexity, but also for providing work arounds for the many bugs and inconsistencies in the language. The database tool kits and file repair utilities seem to exist to fill some huge omissions in the design of the product.

I definitely spend more time tracking down problems and doing work arounds because of bugs in the product, tools and operating systems (reduced reliability). My customers only know that my program didn't work. I have to shoulder the responsibility for these problems.

In 20 years of accelerated evolution in the computer industry, the programmers situation seems to be moving backwards. In the future I am likely to have to invest more time to learn VB for my front end, learn how to apply VFP for middle tier, and SQL server for my database management. It is obvious that the solutions are only going to get more complex and expensive with more room for reduced reliability.