Although I understand the frustration (first hand) working with management, I think it's important to understand that there are two sides to every story.

The stero-typical view of hackers from within management is someone who is too smart for their own good, believes they're above the law, has poor communication skills, and has absolutley no understanding of the realties and constraints of running a business. To management, your brilliant, time-saving tools and techniques are actually the opposite. They waste time, are unproductive, and simply delay the release of something that the client needs *yesterday*. To managment, this is the bottom line (literally). The client won't pay for something that's delivered after they need it.

This view may be completely unrealistic (although this is an extreme version of it), but I think it's important to realise where management is coming from. In my experience, only a small percentage of managers are complete morons, and if your company's worth working for, they won't be around too long. The rest of them just don't see the picture from the same point of view as us.

To me, though, the task of breaking down the barriers rests on the shoulders of both parties. It's important as a hacker to respect and understand the ways your company works. If there are problems that need to be addressed, there are proper channels to go through. If those channels don't get a response, then go to the next level in an appropriate way. By making these small concessions (and others), it's easy to get on in the corporate world.

Management (usually) has the best interests of the company at heart. But unless you can explain your side to them in a way they can relate to, they have no reason to listen.

In reply to Re: OT: Why Hackers dont do well in Corporate World by Mutant
in thread OT: Why Hackers dont do well in Corporate World by mkirank

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.