Kevin Reid's blog

“Redux” is related to “reduce” only etymologically; that similarity was enough that I didn't look up what it actually meant for a long time.

Do not sort the category “Other” under “O”.

“The most important constraint [on naming this] is that it's a good pun.”

$ cat ~/bin/maken

#!/bin/sh
# Make files and view the results.
make "$@" && open "$@"

UPDATE: Turns out I posted this previously, with further thoughts: Avoiding repeating myself (on the command line).

(Images are public domain from Wikimedia Commons: 1 2)

2000 food calories/day ≈ 100 watts

This, for example, is a link: Kevin Reid

This is not a link, but a URL: http://switchb.org/kpreid/

I have a simple guideline for real life interactions with others that carries over quite well on-line, "Deal with issues; ignore details."

It's amazing how well this works in person, especially when trying to get something done. My number one question to another is probably, "Is that an issue or a detail?" We can almost always decide together which it is. Then, if it's an issue, we deal with it, and if it's a detail, we move on to the next issue.

This has also saved me countless hours and aggravation on-line. If I post something and someone disagrees, I quickly decide whether or not it's really an issue and only engage the other if it is. I realize that this is just a judgment call, but I'd estimate about 90% of on-line disagreements are just details. In these cases, I think it's best to simply move on.

— edw519 at Hacker News

I thought this was, even if not necessarily a rule to immediately apply oneself, at least a concept worth thinking about. (Read the further discussion as well.)

I blame a certain English teacher last year for introducing “FAIL” into my vocabulary.