On Tuesday, 01/10/2006 at 12:30 CST, "McKown, John" <[EMAIL PROTECTED]> wrote: > May I be a bit "tacky" (well, I'm going to be anyway). The main > difference that I am aware of between a "sysadmin" and a "sysprog", > other than title and salary, is in the majority of cases, a "sysadmin" > only knows the tools for day to day administration and does not always > really understand the "why" of what they do. I.e. many do things "by > rote" or using a "cookbook". Hopefully, a "sysprog" understands "why" > one does something rather than just "how". Now, a good "sysadmin" will > likely be motivated enough, and hopefully be encouraged, to learn the > "why" so that they can advance.
Exactly. And it isn't tacky to discuss it, it's recognition that employers want to minimize expense and maximize productivity. Productivity, however, eventually hits the "skill wall" beyond which you cannot go without more education and the opportunity to use that education. Scaling that wall is then usually recognized by a change in title and/or salary. Alan Altmark z/VM Development IBM Endicott
