|
Njal, .I don't know if your message was targeted at me, but I can pretend it is. :) you can pretend, but it won't make it true :P .I know the cycle. Then I wasn't talking about you. So There! :-P .I'm in the lucky situation that I can afford to say 'no thank you' tasks that .don't 'suit' me. I would never hire a programmer that admits still using the .cycle for new programs... :) .I haven't written a new report type program (with printer file) in 5 years. .Almost 100% of my new AS/400 programs are server programs serving VB client .programs. Not everyone is that lucky. I was referring mainly to the "hired gun" types - consultants such as me who must get in, jump quickly into 20-30 year old legacy code, fix, change or add to it. If you are lucky enough to never have the occasion to see action like this, more power to you - I wasn't referring to you. My problem isn't with people who don't want to use the cycle on new programs. That is just personal preference. my problem is with those who DO encounter cycle programs, have to make changes to them, and refuse to learn what makes them tick (a 10 minute process) because of some predjudice or hard headed pride. that's just stupid. .A nice weekend to you too! Holy wars are great sometimes! :) already have - it's sunday morning now. Jihad to the great satan, the International Business Machines Corporation! I must now go clean my Kalashnikov :) Rick
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.