Last week, I said that you should practice egoless programming - separate yourself from your programs and accept comments about the code without taking it as a personal criticism. The flip side of this coin is for those who criticize code. Keep your criticism to the code and don't criticize the programmer. All programmers make mistakes and all designs can be improved. By focussing your comments on the code itself instead of the coder, you can improve the code without causing divisions within the team. This works best when you practice egoless programming yourself and allow others to comment on your code without taking it personally. It's all about treating software development in a professional way.
Download