An obvious point that took me way too long to appreciate: in software engineering, you should probably optimize for speed even when you don't have to, because it's one of the easiest/best ways to prioritize subtraction and parsimony in the solution space. https://www.nature.com/articles/d41586-021-00592-0 ….
-
I feel like there are two orthogonal kinds of simplicity: lexicographic/textual and "joules of work done". An ideal solution probably optimizes both and maybe latter is easy to under-prioritize since it's typically less visible.
There is a confounding problem, where everyone thinks they are in an environment where they are minimizing joules of work done, but somehow the joules required continue to increase over time. Yet people do not notice this or question whether they are really minimizing.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.