I have been in extremely similar situations, and I will give some insights as to how I have tackled the (people) communication side.

Mr. Unix

At one place, I was hired as a technical consultant for my VMS skills, although I was also a competent and experienced Unix sysadmin. However, when I joined, I was taking a dead man's shoes role of a Mr. VMS. I found my opposite number on the Unix side very reticent and reluctant to divulge information.

This company was a software house, developing and supporting a product that runs on 6 platforms - C source code served out from a VMS box via NFS. When I joined, although there was a single code base, there was no integrated build process across the platforms. I managed to get the ear of the department manager (who was a good chap), and he managed to psychologically beat Mr. Unix over the head and get his cooperation with my integrated builds project.

Tech services team

At the same company, there was also a team of guys who would go out on site doing installations and upgrades. In many ways, they were doing unnecessary work, as they were claiming huge amounts of expenses for working on site. In practice much of what they did could be done using modems.

A programmer colleague attempted to run a project automating the upgrade and install. However, this required the input from tech services. TS were effectively able to stymie and squash the project.

This team of 7 was disbanded 1 1/2 years later, making 3 of them redundant.

Conclusion

Whoever gets the ear of management has the odds in their favour, and if you don't get on with your boss or department head, it may be resume time.

Try and focus on the business aspects of what you are doing. Put together a formal business case, with a cost benefit analysis. If your line manager is any good, he will pass this straight on to senior management, and you may well find you get more support and encouragement than you bargained for!

Also, if you are doing too much support, and would rather be cutting code, why not say so to your boss? Honesty pays here, because should things get worse, at least you have made your opinion clear. Annual review time is a good time to do this.

My $0.02 --rW

In reply to Re: Greediness, or Paranoia? by rinceWind
in thread Greediness, or Paranoia? by defyance

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.