r/cscareerquestions · 2019
Most-mentioned books in r/cscareerquestions during 2019
This page ranks books by exact tracked mentions in r/cscareerquestions within the published source unit for 2019. 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 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 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.
#4 Clean Code
Robert C. Martin
The book 536 Reddit threads cite when arguing about naming variables — revered by beginners, argued over by seniors.
#5 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.
#6 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.
#7 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.
#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 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.
#10 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.
#11 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.
#12 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.
#13 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.
#14 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.
#15 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.
#16 Fluent Python
Luciano Ramalho
The Python book r/Python recommends when you're done with the tutorials and need to know what the language actually does.
#17 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.
#18 The Effective Engineer
Edmond Lau
A former Quora engineer's framework for shipping work that matters, built around one question: what actually moves the needle?
#19 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.
#20 You Don't Know JS
Kyle Simpson
Kyle Simpson's free GitHub series that bootcamp grads keep crediting when they finally understand closures, this, and coercion.
#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 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.
#23 Accelerate
Nicole Forsgren
Nicole Forsgren's research team ran the numbers on software delivery and found that deployment frequency and stability move together, not against each other.
#24 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.
#25 Domain-Driven Design
Eric Evans
Eric Evans's 2003 blueprint for modeling software around business domains — cited in interviews, assigned in grad programs, rarely finished.