disagree with the everything part of optimize everything. instead we need
a heuristic to determine if something is worth optimizing. i propose a back-of-envelope calculation of how much time you will spend on this in the future; or in practice I go ‘have i done this three times?’
ways of doing things that are optimal in the first place: cache it if it’s free to cache; write down the instructions before implementing.
Did you see the XKCD? The chart there gives a good heuristic because most things you do that are worth optimizing are things you do at some interval.
I don’t understand your second point. My guess at an interpretation is basically look up the optimal solution, but I don’t think that makes sense with caching.
disagree with the everything part of
optimize everything. instead we needa heuristic to determine if something is worth optimizing. i propose a back-of-envelope calculation of how much time you will spend on this in the future; or in practice I go ‘have i done this three times?’
ways of doing things that are optimal in the first place: cache it if it’s free to cache; write down the instructions before implementing.
Did you see the XKCD? The chart there gives a good heuristic because most things you do that are worth optimizing are things you do at some interval.
I don’t understand your second point. My guess at an interpretation is basically look up the optimal solution, but I don’t think that makes sense with caching.
I did see the XKCD and I agree haha, I just thought your phrasing implied ‘optimize everything (indiscriminately)’.
When I say caching I mean retaining intermediate results and tools if the cost to do so is near free.