in reply to Greediness, or Paranoia?
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.
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.
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
|
|---|