slightlyoff@toot.cafe ("Alex Russell") wrote:
One weird trick for improving your web performance!
Develop an understanding of your system such that you can answer *"what is this for?"* regarding any significant fraction of critical path latency.
Good performance is downstream of mastery, which is why complexity is the enemy of going fast: every increment of complexity requires that the team (minimally: all PMs and senior engineers) develop a deep understanding of the new complexity.
You cannot abstract understanding.