------------------------<snip>--------------------------
I agree that techies for the most part don't make good managers. I was
one of those techies that moved into management. I was actually moved
from the position of lead capacity planner to the director of security.
hat was probably too big a jump because I made a terrible manager at
that level and hated coming into work every day. After 2 years I
requested to be moved back into capacity planning and upper management
agreed. As many probably know that didn't really work either because now
I had been "given a chance" and "blew it". No more future of any kind at
that company so I left for a new experience. Personally I'd much rather
work for a good manager who might need some "training" in the technical
areas that a good techie who couldn't manage his way out of the
proverbial paper bag.
---------------------------<unsnip>--------------------
I had a similar experience. But having a know-nothing manager hs
considerable drawbacks. Like a manager that decides to update catalog
management to support multiple level aliases by reading microfiche
listings and creating ZAPS to existing code. He was rather upset when I
refused to support this "pet project" of his. He also didn't like being
contradicted when he made wild claims to management and was informed
that either they were impossible, or they were incredibly risky. When he
delivered an ultimatum to senior management to "do it my way or do it
without me", he was very quickly invited to seek "other challenges".
Nobody really missed him very much.
----------------------------------------------------------------------
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
