|
I partially agree with this. When you become a programmer in a business environment, it does take 3 years to become truly productive. However, MOST of that is learning the business logic and getting good at the techniques required. Once you've already gotten all of that mastered, learning a new programming language is easy. The basics of any programming language are the same... the same algebra is required. The same logic is required. Loops all pretty much work the same. Ifs all work pretty much the same. File access all follows the same general paradigm. The exact syntax may differ, but that's really not that big of a factor. It's changing paradigms that's difficult. Changing from procedural logic (which is possible in any language, including Java and VB) to object-oriented logic is a much more significant change. Or, to a lesser extent, changing from program-driven to event-driven logic is a significant change. But, simply learning to code "DIM" instead of "D-spec" or learning "subprograms" instead of "subprocedures"? Not a big deal. On Thu, 2 Jan 2003, Booth Martin wrote: > > Learning a language well enough to use its benefits is not a matter of a few > hours time on a couple of weekends. It takes at least 3 years of intensive > and hard work with plenty of experience. Of course anyone can crank out > their first "Hello World" program sooner but to be a worthwhile programmer > in the business environment in less then 3 years does not happen anywhere > but in the mind of the self-important. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.