I am starting to get more pissed off than I should be by one particular type of rant on here.

Quote:
My boss/senior/coworker did not know how to do XXX even though he is supposed to have more experience than me. I had to fix his goddamn problem blah blah blah.

If you'd have that attitude on my team I'd be spending a lot of time trying to get you off of it. A team MUST help each other. If you think you're better than others you either teach them or get the fuck out. If you don't understand or know something that's fine and it perfectly normal to have others explain it to you.

Being humble and honest goes a long way in a team.

@Letmecode but teaching them (over and over again) helps the team. Being toxic holds back everyone.

Hmmmmm... I think mostly that type of rant comes from a team member who isn’t valued as person who can teach other team members. I can speak from experience. Nobody knows how to do something, but you do ... and you do it, and then nobody cares. And then they pick it apart and make critiques as if they could have done it to begin with.

@lewdogg I know the feeling, but then it would be appropriate to voice your concerns when it gets picked apart.

I mean it doesn't work when you get pissed about them not knowing stuff when you are actually pissed about the fact that don't appreciate your help.

I know it is difficult because emotions don't work in an isolated and rational way, but sometimes just stopping and reflecting on yourself helps a lot.

@Letmecode not at first you're right. But I don't care solely about direct productivity.

If taking this loss now means we end up with a better team later, it is worth it.

And of course you're right, when the person in question is utterly useless it might be a better idea for them to consider a change in career. But usually this will be clear to the entire team if it is the case.

@ChappIO yeah, that is true.
Hey, part of a bigger problem. Probably an indicator that it is time to leave.

@lewdogg yep

@ChappIO well, if you have to teach over and over again, it's a really good indication that the person should just not be part of this team.
A team should do work, not mutual teaching. Work involves SOME mutual teaching, but not constant.

@ChappIO P.S. But the general rule is right. It's OK not to know. It's normal. It's important to admit ignorance where that exists. Only then one learns. We all make mistakes, and in the past we had made even bigger mistakes. Hell, 8 years ago whenever I had to sort an array in PHP I used selection sort. If I had a hand that could cross time dimensions I would've slapped the shit out of myself. And it's important to correct, teach, and let people around you grow while you grow yourself.

I completely agree.

However, I will not tolerate a colleague that asks the same question more than 2 times. And the second time I'd make it clear that he has to take notes if he's bad with remembering stuff. Third time I'll just ignore the question, and tell everyone to do the same. If the task can't be resolved, or is resolved really badly, it's just better to cut the losses and send that person on his/her way.