3 ms·
IME many web developers do know, but don't do anything because of incentives. Leadership rarely uses the surfaces you make slow, and people don't generally repo
by Hermitian909 3y ago
IME many web developers do know, but don't do anything because of incentives. Leadership rarely uses the surfaces you make slow, and people don't generally report an extra half second of latency. So their incentive structure looks like:
1. They will not be rewarded for going the extra mile
2. They will not be punished for making the site slower
3. They will be punished for shipping the feature slower
Point out "X will be slow" to a lot of devs and they go "I know, but I don't have bandwidth to prioritize the extra work"
Part of why it's so important to make the right thing easy.
- ilyt 3y agoA few, maybe. Most just want to get paid and dont give a shit. Which is normal.
- Hermitian909 3y ago> A few, maybe IME >90% of non-junior engineers understand most of the slowdowns they're introducing and choose to add them anyway. > Most just want to get paid and dont give a shit. My point is that you can't get anyone to give a shit about doing work for which they're not only not rewarded, but actively punished. Expecting people to actively hurt their careers for the sake of shipping good product is not a reasonable expectation. You need some mechanism to fix those incentives.