this is a nasty approach, you have a problem with someone how they conduct themselves or what they deliver you bring it to that person first and you discuss it with them. Only afterwards, if there's good reason to do so, should you escalate to management. Be fair to people and treat people respectfully regardless of what they may have done.
Second, if this company seems to treat people with promotions because of outward appearance. You may want to look for another company that values output first above how someone can politically maneuver.
Full-time web dev; JS lover since 2002; CSS fanatic. #CSSIsAwesome
I try to stay up with new web platform features. Web feature you don't understand? Tell me! I'll write an article!
He/him
apologies he did say that. I was speed reading through it and missed that most obvious part for some reason.
At any event, my recommendation here is to follow the process of development and not circumvent that process by "helping" and "fixing" via out of band mechanisms. Problems such as these need to be made visible on the team boards and then they're signaled by testers and you can do proper fixing that way including educating him on how to do it.
That way you're completely transparant to the whole team and issues are clear where they come from and who needs to solve them.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
this is a nasty approach, you have a problem with someone how they conduct themselves or what they deliver you bring it to that person first and you discuss it with them. Only afterwards, if there's good reason to do so, should you escalate to management. Be fair to people and treat people respectfully regardless of what they may have done.
Second, if this company seems to treat people with promotions because of outward appearance. You may want to look for another company that values output first above how someone can politically maneuver.
The OP says they've repeatedly brought up these issues to the dev, no?
apologies he did say that. I was speed reading through it and missed that most obvious part for some reason.
At any event, my recommendation here is to follow the process of development and not circumvent that process by "helping" and "fixing" via out of band mechanisms. Problems such as these need to be made visible on the team boards and then they're signaled by testers and you can do proper fixing that way including educating him on how to do it.
That way you're completely transparant to the whole team and issues are clear where they come from and who needs to solve them.