r/cscareerquestions · 2022
Most-mentioned books in r/cscareerquestions during 2022
This page ranks books by exact tracked mentions in r/cscareerquestions within the published source unit for 2022. Counts come from the reconciled subreddit-by-month matrix; a source unit may be a bounded sample.
#1 Cracking the Coding Interview
Gayle Laakmann McDowell
The book that turned software hiring into a sport — written by the ex-Googler who introduced programming challenges to the process in the first place.
#2 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.
#3 Clean Code
Robert C. Martin
The book 536 Reddit threads cite when arguing about naming variables — revered by beginners, argued over by seniors.
#4 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.
#5 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.
#6 System Design Interview
Alex Xu
Alex Xu's interview prep guide that one r/cscareerquestions commenter credits with landing his current job.
#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 Working Effectively with Legacy Code
Michael C. Feathers
Michael Feathers wrote the book for the developer who just inherited 30 devs' worth of code across 5 years in 5 different styles and has to ship next quarter.
#9 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.
#10 Modern Software Engineering
David Farley
Dave Farley argues that software engineering is a discipline with repeatable principles — 73 Reddit threads mostly shrug, then mostly agree.
#11 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.
#12 Staff Engineer
Will Larson
Will Larson interviews the staff engineers Reddit wishes it had access to and explains what they actually do after they stop writing code all day.
#13 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.
#14 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.
#15 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.
#16 Python Crash Course
Eric Matthes
The author built it for high school students who kept getting lost — 126 Reddit mentions later, it's still the default first Python recommendation.
#17 Refactoring
Martin Fowler
Martin Fowler's catalog of named moves for cleaning up code that already works, cited 116 times across Reddit in 7 years as the Clean Code alternative people actually prefer.
#18 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.
#19 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.
#20 The Clean Coder
Robert C. Martin
Uncle Bob's professionalism manual: say no to bad estimates, refuse death marches, and work the 40 hours then study on your own time.
#21 The Manager's Path
Camille Fournier
A software engineer picks up a management role and finds out — via 142 Reddit mentions — that nobody told them about the crying, the firings, or the 90-day onboarding clock.
#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 Clean Architecture
Robert C. Martin
Uncle Bob's case for building software that survives its own success, bundled with opinions that provoke more argument than the architecture does.
#24 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.
#25 Elements of Programming Interviews in Python
Adnan Aziz
300 problems, a built-in online judge, and a study guide calibrated to get you through a FAANG coding interview in four weeks flat.