I have always in my 23 years in the IT world found that things like "requirements" and "specifications" were like the lines in a coloring book. I still get to pick the crayons but I'm expected to color within the lines.

Where I work we have a very regimented system whereby we have to ask "mother may I" before doing almost anything that I would consider System Administration 101. But that doesn't stop me from getting my job done. There are always creative ways to work within the system and still get your job done.

I've worked for small companies (less than 50) and very large companies (IBM) and they each bring to the table advantages and disadvantages as far as working for them goes. One company that I worked for there was only 3 people between myself and the CEO and boy could I get work done in short order because I rarely had to get approvals to do anything unless I was spending money. If I was spending money I could get an answer and/or approvals within a couple of hours.

That was OK when that company was small and there weren't many other people making changes in the data center. When the company grew a change management system was essential to maintain everyone's sanity and to prevent us hard charging IT folks from stepping on each other's toes. (example: "What do you mean you're putting that server on that shelf in that rack? I'm going to use that spot!")

The moral of the story is: structure can be a good thing if it is not abused. As long as it doesn't prevent you from getting your job done. It may occasionally slow you down, but in the long run it is a good thing.

Peter L. Berghold -- Unix Professional
Peter at Berghold dot Net
   Dog trainer, dog agility exhibitor, brewer of fine Belgian style ales. Happiness is a warm, tired, contented dog curled up at your side and a good Belgian ale in your chalice.

In reply to Re: Avoiding "brain drain" in the corporate realm by blue_cowdawg
in thread Avoiding "brain drain" in the corporate realm by flyingmoose

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.