[gemstones]

As in software, the best tool for avoiding errors is to not have the software in the first place.

If you must work with someone, or consider yourself to have an ethical obligation to follow this, this is good advice.

If you don't...

Just slowwwly remove your touchpoints with them. Freeze them out. Go through other channels. If you do this right, the person will feel like you have just gradually drifted apart, but won't be able to pinpoint a clear cause.

You don't have to try and get them fired, or anything (and that may backfire on you, so I don't recommend doing it.) But if enough people do this, then they will gradually be the most replaceable person on the team, and they may be let go regardless.

[ramesh31]

>Just slowwwly remove your touchpoints with them. Freeze them out. Go through other channels. If you do this right, the person will feel like you have just gradually drifted apart, but won't be able to pinpoint a clear cause.

Doesn't work if they're leading the project. This is also a very childish way of dealing with problems. Part of your job is to be an adult and learn how to work with people you don't like. Not how to avoid them. It's a critical skill to success in this industry.

[tikhonj]

Sometimes the most effective way to work with a person is to work around them.

Always resorting to that isn't mature or professional, but neither is not recognizing when that's the best option.

[gemstones]

Oh it's not good advice for everyone! If they're a lead on a team you must interface with, they fall into my "you must work with them" bucket, and then the article is pretty good advice.

Eh, I disagree that it's childish advice! It works out pretty well for everyone except the person being frozen out - no matter if you're a child or an adult.