BFatts: A fantastic language-agnostic manual that still applies heavily today. 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

tashoecraft: Great CI/CD book disguised as a novel, inspired me to push heavily for an improved build/release pipeline at work. read comments

a_bonobo: I have to write a lot for my work and this is the best primer on getting things out the door read comments

sarcher: Changed how I approach documenting and completing tasks - in a business like construction where it's hard to go in reverse, it's been a major component of my success since I first read it... read comments

antjanus: The book introduces several basic design patterns, it explains WHY they're used, how to implement them, etc. in the best way I've read so far. No CS book or online article has been... 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

cessor: Kent Beck's TDD is good book to start with. Even if you feel like you have got testing figured out, you should try TDD. It has more to do with discipline and getting things done, rather than... read comments

beat: It's about architecture over time - how buildings change and evolve (and eventually die), to suit the needs of their owners and occupants, and how they deal with the three enemies of all buildings... read comments