25 ms·
I get it and I agree, but my assumption has always been that we're all trying to write the most efficient code anyway right? (Maybe with a few exceptions, like
by waylandsmithers 7y ago
I get it and I agree, but my assumption has always been that we're all trying to write the most efficient code anyway right? (Maybe with a few exceptions, like intentionally slowing down auth to prevent brute forcing passwords). But this article is saying that if I don't, I'm not just a bad programmer, I'm a bad _person_ too. Hm.
- tkadlec 7y agoHopefully that's not the way it comes off! The entire last section of the article is my attempt to make it clear that this _doesn't_ happen because we're bad people. > So clearly, folks who have built a heavy site are bad, unethical people, right? > Here’s the thing. I have never in my career met a single person who set out to make a site perform poorly. Not once. > People want to do good work. But a lot of folks are in situations where that’s very difficult. > The business models that support much of the content on the web don’t favor better performance. Nor does the culture of many organizations who end up prioritizing the next feature over improving things like performance or accessibility or security.