The more clearly you explain to him that he sucks, the more important it will be for him to defend himself. The stupider the justifications that he winds up using in that defence, the more upset he will become, and the harder it will be for him to listen. If you are explicitly holding yourself up as the good example and him up as the bad one, expect his resistance to increase ten-fold.
This is a no-win situation.
You either have to find a way to divorce his ego from his code (likely impossible), or find ways to encourage him to improve while avoiding triggering a defensive reaction (somewhat tricky). It is helpful to be able to recognize when you have triggered defensive reactions that make communication impossible. Then you can try to narrow in on ways to avoid that situation, and ways to defuse it. This will take practice, and I cannot guarantee success. But I can guarantee that success will become more likely.
In reply to Re: Coding styles: OOP vs. Subs
by tilly
in thread Coding styles: OOP vs. Subs
by nikos
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |