3 ms·
> I will purposely challenge their solution to see how they react. > If they get defensive, it’s an immediate no-go. Remember, there’s a difference between def
by mrcncpt 11y ago
> I will purposely challenge their solution to see how they react.
> If they get defensive, it’s an immediate no-go. Remember, there’s a difference between defending which is good and being defensive which is bad. The difference is that the former is based on rational facts, the other is based on emotion.
Are you always able to challenge them based on "facts", or are you going to challenge them with your current world view? I can see someone getting defensive if your challenge is perceived as deliberately provoking.
- pc86 11y agoIf you're submitting something for review which is admittedly going to be used at least in part to decide if you are "good enough" to hire, it would be foolish not to expect to have to defend the choices you've made. Using the author's definition, "being defensive" based on emotional responses is more a character trait than anything else, and a negative one at that. I would much rather work with a slightly above average or average developer who is thoughtful and rational than a rock star who gets personally offended if you question their use of $DESIGN_PATTERN.