Kernel Hacker's Bookshelf: The Practice of Programming

I read Rob Pike's "Notes on Programming in C" way back in the day, and it is still one of the
very best essays on programming style I've ever read.  I credit this with almost
single-handedly banging me upside the head and causing me to consider my code more like a
novel than a flowchart: how can I write my code so that its structure and intent can be easily
SEEN and UNDERSTOOD by the reader?  How can I make it obvious which things are important and
which are incidental, just by the way I write the code?  This is catnip to a naturally
anal-retentive person like myself.

Of course I've read "The C Programming Language", and I also had an opportunity to hear Brian
Kernighan speak at Carnegie Mellon in the 80's, about C++ (although back then it wasn't clear
this would be the name!)

If these guys are giving advice, I'm buying!