Though in the past I would agree with you, I no longer do. I've graduated to a XXXXL clue stick for the programming staff with NO RESULTS. The current crop seem to have the attitude of "it should work the way that I think it should work and want it to work. I don't have time to be bothered. I'm too busy as it is." I blame the Web and MS for this "instant gratification" desire in IT and end-users.
Perhaps we should stop calling them programmers and considering them technical? Maybe I'm being a bit too harsh, but perhaps part of the problem is that we still insist on giving people technical titles and responsibilities (from decades where they actually meant something) to people that are, at best, administrators.
I realize that there have always been problem individuals, or people with fewer that the desired skills. But, in truth, I have never heard more whining from people that have access to the best tools and technology available, yet they can't seem to figure out how to code an IEBGENER job stream. Even worse, there has never been more documentation available than there is today, yet the average "programmer" doesn't seem to realize that (just like books), PDFs don't read themselves. In the past many people were accused of only copying the examples from manuals rather than reading them, yet in many ways I wish the current crop would be even that industrious.
I also recognize that there are exceptions to this rant out there and to them I apologize for my statements and wish them much luck.
My two cents Adam ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
