Subreddit
Top books from r/gamedev
r/gamedev is a community for professional and hobbyist game developers discussing engines, design, code architecture, and the business of making games.
Updated August 2026 — rankings refresh with each new pull of comment data.
About this ranking
Game Engine Architecture dominates with 45 mentions — nearly double the second-place Theory of Fun for Game Design (24) — which tells you this sub skews toward builders who want to understand the machinery, not just ship something. Design Patterns at 20 mentions lands higher here than in any other sub except r/cscareerquestions, reflecting game programmers' obsession with component systems and state machines. The Mythical Man-Month and Cracking the Coding Interview both chart, but at 13 and 10 mentions respectively they're afterthoughts compared to r/ExperiencedDevs where they pull 99 and 76. r/gamedev reads fewer career-ladder books and more craft-of-engines books.
By year
Most-mentioned in r/gamedev
Ordered by tracked mention count across all published years. Sentiment is shown as context and does not change the order.
#1 Game Engine Architecture
Jason Gregory
Jason Gregory's map of every system inside a AAA engine — memory, audio, rendering, physics — written by someone who shipped them at Naughty Dog.
#2 Theory of Fun for Game Design
Raph Koster
Raph Koster's 2004 illustrated argument that games are just pattern-recognition engines, and fun is the brain's reward for learning a new one.
#3 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.
#4 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.
#5 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.
#6 The Design of Everyday Things
Don Norman
A cognitive scientist argues that when you can't open a door or use a stove, the door and stove are broken — not you.
#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 Clean Code
Robert C. Martin
The book 536 Reddit threads cite when arguing about naming variables — revered by beginners, argued over by seniors.
#9 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.
#10 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.
#11 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.
#12 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.
#13 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.
#14 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.
#15 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.
#16 Hooked
Nir Eyal
Nir Eyal's blueprint for building products that keep users coming back — and a map of exactly how apps have been rewiring your brain.
#17 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.
#18 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.
#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 Lean Startup
Eric Ries
Eric Ries tells founders to ship a broken version on purpose, collect data, and repeat until the market stops ignoring them.
Looking for more? Similar subreddits
Subs whose top-mentioned books overlap most with this one.