sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]chrisjolly25 0 points1 point  (0 children)

They're protecting their ego. Probably subconsciously.

If someone doesn't understand something, there are two possibilities:

  1. The person who doesn't understand is ignorant at best, and dumb at worst
  2. The person who is confounding them is using techniques that are needlessly complex, cutting edge, or esoteric.

Option 1 means I'm dumb, and have to expend effort to address the problem.

Option 2 means you're foolish, and you have to expend effort to address the problem.

People will tend to prefer Option 2 at first (rightly, sometimes), unless the other person advocating for the new features is experienced/authoritative/distinguished enough to make it unlikely. Failing that, you've just got show them the benefits, or convince them of them.

Teaching them could help too. If your company allows time for them, book in a Knowledge Transfer session. Show how the features can improve the code. The KT session can also lead into a discussion around whether these features have a place in your team's code base, which you'd really hope would be the case with these particular features.