"People vs. People"...sigh...that's called politics.

Your story cites several political problems that originated with interactions based on development you were doing.

Basic Rules for Developers Entering a New Development Environment

1. The person(s) who ha(s/ve) been there before know something you don't. Find out what it is. In particular, find out how they've been doing things, and ask why they did it that way (look very puzzled, NOT like a code hawk that just found a juicy bug).

2. Until you've completed rule #1, do not volunteer for anything, and keep your mouth shut in all public meetings (unless you can ask a question to advance the completion of rule #1).

3. Do EVERYTHING you're asked to do, EXACTLY as you're asked to do it, until you've completed rule #1. Make sure to get a complete list of all work products you are expected to produce. Make sure to ask if any standards or examples that your boss likes are available for you to review and imitate. Slavishly imitate these work products, while making sure any information YOU consider important is ALSO included. Don't get caught in noncompliance with precedent when you're still finding out what the precedent is, why it is, and how it became that way.

4. Once you've completed rule #1, never do more than one new thing at a time. Do your best to discuss it with the people most likely to object, and if they seem to take it as their idea during the course of the discussion, APPLAUD their idea, thank them for their input, and ask if they'd please comment on your work as you implement "their" idea.

The list can go on, but these four, all dependendent on #1, are the mimimum necessary rules to keep from making powerful political enemies by your own actions before you are ready to make these enemies by your own choice. And that, my friend, is another lesson entirely.