censhin: I think it's far undervalued. Definitely a must read. The Ruby written could be completely replaced by pseudo code, and it wouldn't change the lessons taught. read comments

HeckFeck: If you're interested in something closer to the hardware than Python, why not read about the language that implements Python? It's a programming classic, very concise, easy to read and... read comments

cfeduke: If you had to pick between SICP and Clean Code because time is at a premium I'd err on the side of Clean Code for practicality. Writing maintainable code is paramount. read comments

mindcrime: If you didn't take, or have forgotten, classes like Computer Architecture or Digital Logic, this is a great book for getting your head around the low level details of what's happening in side a digital computer... read comments

apo: Would be an example from software architecture. It catalogs a couple of dozen patterns that recur in projects regardless of their specific domains. read comments

BFatts: A fantastic language-agnostic manual that still applies heavily today. read comments

organsnyder: Good for learning the mindset of developing backward-compatible APIs in any language read comments

carapace: IMO this is the most concise yet accessible gateway to the inner Mysteries of Computer Programming. Read between the lines, the prime thesis is implied not explicit. read comments

cben: This gives you a phenomenally good survey of concepts and practice of distributed systems... read comments

ereyes01: One of the most important books ever written on software engineering practice. Author Frederick Brooks won the Turing Award for this book and for his work on IBM's System/360... read comments

rubiquity: Is one of my favorite books, too. That book really motivated me to learn how programming languages work. read comments

cfeduke: Is older but relevant and clearly describes concurrency on the JVM. A must read for any Java, Scala, Clojure, etc. software engineer; well-written, enjoyable, concise. read comments