News for hackers. Stuff that matters.
Re:Ask HN: Is it ever OK to completely unleash on incompeten... by avenger123 on Sunday August 11, 2013 @03:27AM (#6194201)
Well, first of all, are you the only one noticing the incompetence? If so, why is that? Why is isn't someone in a position of authority involved? This would be the first step. Let them know and voice your frustration but make it sure it comes across as a concerned voice for the company and not a vendetta against the person.

If you are the only one that believes the person is incompetent but the rest of the team (including supervisors) doesn't believe so, then you've got to let it go. It's not your battle.

If you want to "thunder down" on the individual, go ahead, just don't do it in front of the person. Find a room in your house, and let it out. You'll feel almost the same as if you had done it in person.

People have long term memory for highlights and short term for details. If you "unleash" you could be branded as the person that torn down another colleague (a non team player, hostile, etc..) and the reasons for your outburst (regardless of how legitimate, wouldn't be really remembered). Depending on where the person is on the totem pole in the company you may even be putting yourself in danger of losing your job.

But, based on what you are saying, it almost seems you are talking about design issues with code and approaches on how to solve a problem. If this is the case and you think the person's solutions are sub-par, but they still get the job done, then you just need to chill. We love to think how something is designed/implemented is really important but at the end of the day if the car turns on and drives around, most people just don't give a sh*t that the engine is the best in the world. Keep your part of the code the way you and if it turns out that you end up maintaining/owning the person's work, then you can start refactoring or complaining that the code is subpar.

There are no comments on this comment yet.