You're right I would just add :
Inability to delegate. A bad technical leader think that as he can do it better, he should do it.
This prevent him from doing his jobs (make his TEAM produce better) beccause he will have less time to transmit his knowledge, plan/coordonates things...
The worst effect to this behaviour is to my mind that the coders feel under-estimated (and in a sense it's the case) and this tend to act on their mood and so on their productivity...
NOTE : I just like to precise what I said earlier, I don't think that technical manager are better, I say that I met more tech-manager in the good managers group than non-tech ones.
Of course a good tech guy won't automatically make a good manager, but I still do believe that it will be even harder for a non tech one, and I guess that you all know why (haven't you deal with commercial manager ? Financial one ? ;-)
"
Only
Bad
Coders
Badly
Code
In
Perl" (OBC2IP)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.