I borrowed this book from the library, both because it happened to show up in a catalog search, and because I recognized him from Poker Superstars II. Format is the Who Moved My Cheese? of poker. I see it as a motivational quick-read vs. providing detailed stategy: about 10 pages for each game, large print, with 1/3 page blackboards summarizing main points. The book is short enough that there's no risk in picking it up and reading it: at 150 large print pages, it's a quick read.
The classic software engineering essay collection turns 20 years old. Interesting perspectives from 1975, 1986, and 1995. "Four new chapters" Chapter 18 is a re-examination of the original 1975 essays. Some minor clarifications are brought to light by time, but most assertions still prove completely true.
I've decided to go with a remote tactic that's slightly more reliable than my previous tactic: Name the gvim server by the contents of the $DISPLAY variable. I have side-by-side PCs with their own X-servers, so I want to send the file to the gvim server that is outputting the same place as my cscope session. I now grep the $DISPLAY out of the gvim server list, to determing whether I am going to set up a new server or use an existing one.
gvim --serverlist | grep -i "$DISPLAY" 2>/dev/null
if [ $? -ne 0 ]
gvim --servername $DISPLAY $*
gvim --remote-send "<ESC>:sp $CSCOPE_ROOT/$2<CR>:0<CR>:$1<CR>:-1<CR>" 2>/dev/null
After making it through More Than Enough, I finally understand the structure. If you do read this book, don't cheat yourself by skipping the cumulative review sessions at the end of each chapter. They help reinforce a mindset that is a key to getting your priorities in order.