helpful in fact it is very negative and confrontational. 2. Tells what but not why. 3. Explains what, why and also where this can be applied in future.
point by looking at the what not the why. Normally DPs are a choice they have trade offs. Does it really need to be a singleton or is that just personal preference? Focus on the facts, especially in a position of authority.
we fix this method, our lives will be better @anigelUK Developers are people. They feel protective of their code. They can get defensive if they feel attacked. They may shut down and stop listening, certainly not learn well. Not everyone has same understanding of code base or features. Develop not destroy. Especially more junior ppl
*must* be flagged up, changed or fixed. Pick up on the most important things. If it really makes a difference then fix it. Bonus point. Don’t say “While you are at it fix X” in code that wasn’t changed. Raise another issue for it.
boss @anigelUK Craig’s boss gave the craigslist founder some advice that Craig shared in a Business Insider interview. When it matters a lot--when there's something on the line; when it's going to affect something important at the company; --of course let someone know. But when it doesn't really matter, don't tell people what they're doing wrong. Let them be.