3 ms·

> A team with a bad developer is way better off short one developer than it is with a bad element. How do you know that you just didn't communicate your issues

> A team with a bad developer is way better off short one developer than it is with a bad element. How do you know that you just didn't communicate your issues well to the person? Is there a way to help them, you and your relationship improve so that you can be a stronger team? We all have blindspots and weaknesses, and weaknesses that fit together like puzzle-pieces tend to find each other until you resolve them. The half-moon is only an illusion, the whole moon is still there. You just don't see it, and you need the whole.

stronglikedan 8y ago
> How do you know that you just didn't communicate your issues well to the person? When you encounter that person, you'll know. Some people just aren't capable of grocking certain things. I had a guy on my team like this. He just wasn't getting it. At first, I would spend extra time with him, communicating the issue from every possible angle. He would almost always end up producing something so far off base. Everyone else on the team was sync'd but he just never got it. The best part is that he refused to believe that he was incompetent. I say "best", because that gave me an easy way to get him to move on without firing him. I knew if I wrote him up one time, his pride would kick in, and he would start looking for another job. The plan worked perfectly.