Subreddit
Top books from r/compsci
r/compsci is a subreddit for computer science theory, research, and foundational topics, drawing students, academics, and engineers interested in the discipline's intellectual core rather than day-to-day coding practice.
Updated August 2026 — rankings refresh with each new pull of comment data.
About this ranking
The top recommendation here is SICP at 86 mentions, which also appears in r/learnprogramming (166) and r/programming (48), but r/compsci pairs it with Introduction to Algorithms (70) and The Art of Computer Programming (62) — a combination that signals serious algorithmic study, not career prep. Contrast this with r/cscareerquestions, where Cracking the Coding Interview dominates at 525 mentions and SICP doesn't register at all. Code: The Hidden Language lands at 42 mentions, higher here than in any other sub, reflecting a taste for foundational explanations of how computers actually work. The practical staples that dominate neighboring subs — Clean Code, The Pragmatic Programmer — barely surface.
By year
Most-mentioned in r/compsci
Ordered by tracked mention count across all published years. Sentiment is shown as context and does not change the order.
#1 Structure and Interpretation of Computer Programs
Harold Abelson
MIT's 1985 Scheme textbook that 319 Reddit commenters have recommended and a noticeably smaller number have finished.
#2 Introduction to Algorithms
Thomas H. Cormen
The textbook four MIT professors wrote to settle every algorithms argument, cited by 254 Reddit commenters across 12 subreddits and still going.
#3 The Art of Computer Programming
Donald E. Knuth
Donald Knuth's multi-volume monument to algorithms: the book programmers cite in library lists and almost nobody finishes.
#4 Code: The Hidden Language of Computer Hardware and Software
Charles Petzold
A retired software engineer builds a computer from telegraph relays and flashlights, one chapter at a time, until you understand what a CPU actually does.
#5 The C Programming Language
Brian W. Kernighan
The 1978 book that defined C's syntax, co-written by its creator, still cited by name 281 times across Reddit in 7 years.
#6 Modern Operating Systems
Andrew S. Tanenbaum
Tanenbaum's textbook walks through every layer of an OS — scheduling, memory, file systems, threads — one chapter at a time, with the implementation details left in.
#7 The Pragmatic Programmer
Andy Hunt
Two veterans hand you a checklist for the craft: don't write code you don't need, own your tools, and fix the broken window before someone else does.
#8 Designing Data-Intensive Applications
Martin Kleppmann
A backend engineer's field guide to the tradeoffs behind every database, queue, and distributed system you will ever touch.
#9 The Soul of a New Machine
Tracy Kidder
A journalist watches a team of engineers at Data General burn themselves out building a minicomputer nobody remembers, and writes the definitive account of what that costs.
#10 Computer Networking: A Top-Down Approach
James F. Kurose
Kurose and Ross walk the network stack from HTTP down to the wire, so the physical layer arrives after you already understand why it exists.
#11 Computer Systems: A Programmer's Perspective
Randal E. Bryant
The CMU course-in-a-book that pushes programmers to read assembly, defuse a binary bomb, and stop pretending they understand what happens after main() returns.
#12 Design Patterns
Erich Gamma
The 1994 Gang of Four catalog that named 23 object-oriented patterns, gave developers a shared vocabulary, and taught a generation to over-apply both.
#13 Eloquent JavaScript
Marijn Haverbeke
Marijn Haverbeke's free online JavaScript book — variables to async in one volume — by someone who said he wouldn't wish a game-programming career on anyone.
#14 The C++ Programming Language
Bjarne Stroustrup
Bjarne Stroustrup's own manual for the language he built — 1,300 pages that explain every design decision, including the ones you're cursing right now.
#15 The Mythical Man-Month
Frederick P. Brooks Jr.
Fred Brooks spent the 1960s building IBM's OS/360 and wrote down everything that went wrong — in 1975, and it still lands.
#16 The Phoenix Project
Gene Kim
An IT manager inherits a failing project, a mutinous ops team, and a CEO deadline — and has to ship before the company does.
#17 Code Complete
Steve McConnell
Steve McConnell's 900-page construction manual for software, ranked third on Reddit's canonical reading list and still cited 25 years after publication.
#18 Effective Java
Joshua Bloch
Joshua Bloch's item-by-item case for writing Java the way the platform was designed to be used, with 90 independent recommendations that aged better than most of the language.
#19 Pattern Recognition and Machine Learning
Christopher M. Bishop
Bishop's 2006 Bayesian ML textbook: 26 of its 39 Reddit mentions come from r/MachineLearning, where it sits permanently on the serious-math shelf.
#20 The Linux Programming Interface
Michael Kerrisk
A 1,500-page tour of every Linux system call, written by the man who maintains the manual pages.
#21 A Mind for Numbers: How to Excel at Math and Science
Barbara Oakley
A failed math student becomes an engineering professor, then writes the manual on how the brain actually acquires hard skills.
#22 A Philosophy of Software Design
John Ousterhout
A Stanford professor's 200-page rebuttal to Clean Code, built on interface depth rather than method length.
#23 C++ Primer
Stanley B. Lippman
The 1,000-page C++ textbook that r/learnprogramming recommends by name whenever someone asks how to learn the language seriously.
#24 Clean Code
Robert C. Martin
The book 536 Reddit threads cite when arguing about naming variables — revered by beginners, argued over by seniors.
Looking for more? Similar subreddits
Subs whose top-mentioned books overlap most with this one.