Many times if management is not computer literate, words will have little impact because they don't understand the entire development process. Convincing them seems to depend on how willing they are to learn, how willing they are to trust you, how able you are to verbalize, and how much time you have to prove your point.

Being a hardcore geek with no appreciable verbal skills, I've never been good at this in the past. Luckily at the moment I have a good boss that is very computer literate.

For example, one big problem is that many don't grasp how hard development really is. Even if they grudgingly admit, from past experience and anecdotal evidence, that it is hard and takes a long time, deep down in their heart many don't understand why, and are unwilling for whatever reason to find out why. I can only assume this is because they've never had to go through the design/write/test/debug/test/release/take some heat/fix/rerelease/maintain process themselves and boil it down to just the "write" phase.

Unfortunately, I've seen this manifset itself as distrust of the programming staff ("Those slackers have been writing that new OS for over two whole weeks -- why isn't it finished!?" :-). For more in-depth analysis, see Dilbert...

bluto

In reply to Re: Lost in the Translation by bluto
in thread Lost in the Translation by Mr. Muskrat

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.