> And if you try to write the 20x faster version, your coworkers will think you are over-complicating and not being a team player.
Hear hear!
Why is it like this?
nerdponx
Because spending tens of developer-hours to save tens of compute-hours usually isn't worth it. Justify to me that it's worth the time investment, maintenance burden, and risk of failure, then I'll let you work on it.
cmrdporcupine
Because 9/10 developers would not implement it correctly anyways (even if they think they did) and the generally-right thing to do is rely on existing libraries and services which do this already.
Hear hear!
Why is it like this?