On the whole I agree with stephen the personnality is the most important.
However my experience lead me to think that technical managers tend to have a better understanding of the work to do and hence make better choice when they have to choose priorities, estimate the developpement time, make the best out of other programmers...

I had 'commercial' managers who told me :
'What 4 days ? Rewriting this (entire) programm for only 4 (6) platforms will take you 4 days ? Just skip the tests, you'll have 2 days...'

Usually an technical guy will understand and rather say it like that :
'Ok just drop the less important features for the moment, I'll try to get one more day saying that the 5 others platform weren't in the specif. But please double check your test, it must be clean.'

It may seem a little bit exagerated, but it's often like that for me.

And usually good (tech) manager don't tell you things the way they didn't like to be told when they were only coder and that's a REALLY good thing.
I'm one of those who thinks that you can say almost anything, but that you're better listened when you're not hurting your listener.

"Only Bad Coders Badly Code In Perl" (OBC2IP)

In reply to Re: OT: Tech Managers vs. Non-tech Managers.. by arhuman
in thread OT: Tech Managers vs. Non-tech Managers.. by LD2

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.