✳flâneur — a map of the web's best reading
Performance Is Not a Technical Problem - Shu Ding
shud.in · 1,071 words · saved by 1 readers
After 400 performance PRs, I learned the problem isn't code or tools—it's entropy. And you can't fix entropy with a patch.
Performance Is Not a Technical Problem Over the past 7 years at Vercel, I have opened ~400 pull requests focused on performance. 1 in every 10. Waterfalls eliminated. Bundle sizes cut. Cache keys fixed. Re-renders removed. People ask me why. They think I am fixing broken code. I thought that too. But over time, I learned something: these are not technical problems. The same mistakes kept appearing. Different engineers. Different codebases. Different times. We have faster frameworks. Better compilers. Smarter linters. Performance still degrades. The problem is not the code. The problem is not t
Explore this link on the map →related reading
- abseil / Performance Hintsabseil.io
- AddyOsmani.com - 21 Lessons From 14 Years at Googleaddyosmani.com
- https://danluu.comdanluu.com
- The Law of Leaky Abstractions – Joel on Softwarejoelonsoftware.com
- Choose Boring Technologyboringtechnology.club
- claude code is not making your product betterethanding.substack.com
- Notes on Distributed Systems for Young Bloods – Something Similarsomethingsimilar.com
- Thoughts on slowing the fuck downmariozechner.at
- That's not an abstraction, that's just a layer of indirectionfhur.me
- Essays on programming I think about a lot | benkuhn.netbenkuhn.net
- Less Snake Oil, More Context — surma.devsurma.dev
- abseil / Performance Hintsabseil.io