3 ms·
In my career, I have had to deal with other senior developers who would throw tantrums whenever I pointed out something problematic about their code. Obviously
by ourmandave 5y ago
In my career, I have had to deal with other senior developers who would throw tantrums whenever I pointed out something problematic about their code.
Obviously how and when you point it out matters. Like in the middle of a user demo.
"Why does it let me enter Feb 30th?"
"Oh, Dave wrote the validation on that. What was your thought process on that one Dave?"
- kwertyoowiyop 5y ago“Making sure our QA Department is worth their budget, Steve.”
- whatshisface 5y ago"Future-proofing for the introduction of leap months."
- tonyedgecombe 5y agohttps://www.timeanddate.com/date/february-30.html https://www.timeanddate.com/date/february-30.html
- epolanski 5y agoWhy's there so many devs at a user demo?
- Jtsummers 5y agoAnother way to say this, which should be common sense, is don't call people out in public unless the intent is to embarrass them. Which is, of course, an asshole thing to do. If you spot an issue, you raise it in the appropriate forum. This could be a one-on-one, feedback through whatever review system you use, or feedback in a review meeting if that's used. But calling it out in public, especially in front of a manager (more than one level above) or a customer is a great way to demonstrate that you are, well, an asshole.