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.
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.