This is great! In re: time is money, it's even worse than that: attention is money. The quality of time varies with the "self-remembrance" if you will. - - -

This is great! In re: time is money, it's even worse than that: attention is money. The quality of time varies with the "self-remembrance" if you will. - - - - Take time to "pop the 'why?' stack. In practice many of us are "yak shaving" and wasting a lot of time and effort on "low-leverage" actions. > yak shaving > [MIT AI Lab, after 2000: orig. probably from a Ren & Stimpy episode.] Any seemingly pointless activity which is actually necessary to solve a problem which solves a problem which, several levels of recursion later, solves the real problem you're working on. ~http://catb.org/jargon/html/Y/yak-shaving.html http://catb.org/jargon/html/Y/yak-shaving.html - - - - The most metal programmers I know type hella fast. One guy in our office, we would play hangman and the only way to beat him was to figure out the word before he did, because the millisecond his brain "got it" you would hear a small explosion as he typed the word on his clicky keyboard in a single motion. If you figured out the word at the same time as he did he won. SOB could also write bug-free C++ by the page. At speed. Another guy I knew had a tiling WM and only used terminals. A vim man, he could type slightly faster then the system could respond, emitting a single stream of characters that flowed smoothly from vim to wm to shell and back again, his locus of attention flying around too fast to follow even if you knew what he was doing (editing and recompiling or whatever.) - - - - (Ooooo... Major points off for deep linking to XKCD without attribution. Bad pool. It's probably one of the most important and useful XKCD comicS. "Here’s an old comic..." ah, that's cold blooded.) Other than that, this is the best general advice for programmers that I've seen for a while. Yay!