Why do shops with legacy teams hire outside contractors? Because the legacy team cannot deliver. Of course we have to go through the interview, and make the "team" think we're mano `y mano with `em. But we know the truth - we're being hired cause the team can't deliver. Team shop politics. We have to pretend awfully hard that manure smells like roses. I do it automatically now. Even have a little list of "team" icebreakers and platitudes designed to make a less than adequate group feel worthy. We can't take it seriously - we have to hide our laughter - but we should not show contempt - that legacy team is the apex of a carrer for many developers. Not everyone has the same skill levels.

PS - They hate us even more when our modules are delivered - they have to go sit in front of the boss and tell him why they couldn't do it:-)

Team Politics and outside contractors - an eveolving reality of our times:-)


>Hi bruce,
>
>I appriciate your message and I agree that it has to be that way *if* people have to work with eachother. Of course the situation on the UT is slightly different. However it is a very risky situation that does not always have a good end. I personally have been in such situation before, beeing the one (of two) that questioned the course of their Y2K solution in FPW. It was explained as me beeing a bully and I was sacked. Another person who agree´d with me (Also an fairly known UT member up here) was worked out a few months later.
>
>Personally, I did not care that much, since I did have enough work. If people do want to have a yes-nodder type of developer, they should not hire me. OTOH if they want have a dedicated, experienced and intelligent developer, they should not complain if this developer has some remarks on your current applications, course or programming team.
>
>Walter,