3 ms·
As one develops as a programmer, the performance floor of your code should increase. In those early years, you might waste inordinate time squeezing out a 3% pe
by norir 3y ago
As one develops as a programmer, the performance floor of your code should increase. In those early years, you might waste inordinate time squeezing out a 3% performance improvement in an existing feature when you could instead focus on building the next thing that might potentially double the product market. As long as you eventually see the light, I don't think this time is wasted because in chasing those small efficiencies you will learn the high level patterns that lead to good enough code as well as the evil of premature optimizations.
Also, you will never get a bonus in proportion to the cost savings of an optimization.
- ajmurmann 3y ago> I don't think this time is wasted because in chasing those small efficiencies you will learn the high level patterns that lead to good enough code as well as the evil of premature optimizations. How many times in your career has a PM agreed to make room in the backlog to prioritize performance work? It very rarely happens and the reason is that costumers rarely care. It's catnip for developers and I love doing it, but it's rarely something that matters enough