>often people ostensibly work with the team, but actually want to see the team fail I've definitely seen this as a very common proclivity of small, poorly stru

>often people ostensibly work with the team, but actually want to see the team fail I've definitely seen this as a very common proclivity of small, poorly structured teams, over 30+ years of software development experience. "Buy-in", or .. the phenomenon of staff actually buying into the project, and investing themselves in the effort required to realize a particular vision, actually requires them to agree with the project policies and strategy. If people in the team do not agree - like, actively, not just saying 'I agree' - not much work ever really gets done. People who feel they have to covertly work to make a team fail need to realize where the failure really starts: in the decision to do so, without communicating about it. Whereas, on the other hand, teams who really like each other - enjoy the project - use the technology well - and are open about the things they do not like about their daily/weekly work load - often accomplish amazing things. It all starts with the decision to make something happen. If that decision is made for you by someone else, either buy the decision or don't. Loitering around to 'do the right thing and destroy the project/be there when it "inevitably fails"' is quite a disastrous contribution, in my opinion. I encourage everyone I work for - subordinate or superior, or otherwise - to keep things clean. Work, or leave.