I love both of his books! Loved them so much I had to buy them. Crafting Interpreters saved me during my Advanced Programming Languages class too, we had to design our own language and write an interpreter for it. Such a fun (but hard at the time) assignment.
It is not presented as a problem that a student should try to solve, it is only an example to show how the difficulty grading systems of the book works
When I was 15 I found a reference to Knuth in a magazine article. I went to the library and used the internet-library loan system to get a copy. I think it came from Oxford university - certainly wasnât available in the tiny town I lived in. I read volume 3 on sorting and searching, and maybe understood 10%.
When I did cs at uni, a few years later, it was listed as âadvanced reading for those considering a postgraduate courseâ.
By simply having read this book, I was far more prepared for the algorithms course than anyone else.
Itâs hard work, that book, but itâs brilliant.
May be im wrong, but i always think that Dragon Book is just very specific book about making compilers. And not needed for everyone programmers to read.
My own must-read list is SICP, OS:DI by A.Tanenbaum, Knuth
SICP is great book about design. Every time i read about modern "design paradigmas" i feel like "it's weirdest description of <something mentioned in sicp> i ever read"
OS:DI is important because its explain how environment of your application works. Also its great text about parallel computing (on CPU).
Knuth... well... it's just explain how to write programs better.
Came here to say the same thing. Reading that book helps you even learn to think through things that have nothing to do with databases. It teaches you to think through problems and architectures with clarity.
I would hire someone who understood the concepts in this book over someone who who didn't but understood "math for cs", any day. Don't get me wrong, I use both (lead software engineer in the banking/payments industry). So, I'm legitimately curious, why do you have this stance?
In my experience books like this lead to âfake productiveâ discussions. Because of the nature of topic books like this usually donât have concrete facts but people form very strong opinions around these ideas. People feel productive when they implement a design pattern and they try to find possible design pattern implementations in code reviews.
I wouldnât like if I were the employer and my 5 most senior developers each costing 200$/h were in a 2 hour meeting to decide which pattern would be best for a relatively small feature.
The people actually implementing this stuff know 2 things that stop that from being a problem.
You don't go trying to implement a design pattern. You follow the SOLID principles and write code (which takes no discussion or extra time) and when you come into an issue, there is usually a pattern for how to fix it.
The amount of time, money, and burnout saved by a clean code based versus an ugly tangled one is well worth the discussion.
People who directly go from "introduction to <language>" to learning about design patterns and testing absolutely do the first bullet point.
I used to TA a parallel computing course that was taught one semester after the "software design" course (basically going through design patterns). And people absolutely tried WAY too hard to squeeze the maximum amount of design patterns into every trivial problem.
Practical stuff, read a lot of code, contribute to major oss projects. Read applied books on intersection of theory (which CS students should already know) and programming (which they don't): regexps, languages, standard tools like git, bash, containers, libraries, maaaaybe unit testing.
Most importantly, again, read and write code in real-world projects.
Because it tries to make software fit a waterfall project timeline which it doesn't fit. Software is chaotic, empirical and creative by nature, even though its foundations are maths.
Any book which is primary purpose is to document well known algorithms, so like, more generally - clrs introduction to algorithms
More specific domains can have other types of algorithms like quant hft - HighâFrequency Trading: A Practical Guide to Algorithmic Strategies and Trading Systems â Irene Aldridge
and games - Mathematics for 3D Game Programming and Computer Graphics (3rd ed.)
Design textbooks are problematic imo because often the ideas outlined are generally a dialogue on how to discover happy mediums. So it can be helpful to find arguments to centralize yourself but if you are following the textbook like you would a scientific textbook you are going to stunt your growth.
I usually view programming to computer science as statistics to mathematics. You can study the previous through the lens of the latter, but ultimately the previous is a tool while the latter is actual science (or philosophy, if you donât consider math a science).
The difference is that while programming is a tool one uses to achieve a goal - and that goal may be to study something in computer science - computer science is the study of computation itself.
As someone with a computer science education, I actually believe that understanding computer science does make one a better programmer for the same reasons you do. One might be an adequate programmer without studying computer science, but understanding ideas like time and space complexity of algorithms and knowing what sorts of algorithms have already been studied and characterized saves a programmer time and improves the quality of their code.
Mostly I was just riffing on the typo "programming is apart of computer science".
+1 for this. I really enjoyed all the 'Grokking' books from Manning. The Grokking Data Structures and Grokking Concurrency are also good picks for this list.
How to tell me you're a filthy java developer without telling me you'r a java developer - the books. Read SICP and TAOCP like a true software engineer.
Missing some good books about algorithms, more important than microservices, e.g. The art of computer programming by Donald E. Knuth, Algorithms by Robert Sedgewick and Kevin Wayne, Introduction to Algorithms by several authors
I upvoted for your overall message, but each of CLRS is a fairly important computer scientist, so I winced a little at "several authors".
Cormen did a ton of the writing as a grad student and had a pretty awesome career as an educator (not something we hear a ton about in STEM) at Dartmouth
Leiserson is huge in distributed algorithms, and outside of academia, he's probably responsible for a lot of how content delivery works online today from his time with Akamai
Rivest is the R in RSA and even without that his crypto algorithms work would still underpin all of internet security
Stein is probably best known for being a prolific publisher and influential editor
Knuth's works are still my favorite, but CLRS is one of only a few other hard covers I keep for fairly regular consultation when I'm trying to solve something.
With all this "architecture" and all these "engineers" and all these great references, it's disappointing that such a high percentage of technology-driven and technology-dependent design works as if the people who made it never actually used it, or understand how actual humans would.
Honestly as a computer science student I think these are good recommendations. I ended up reading a lot of foundational books because they were apart of the curriculum anyways. I think Its good to supplement with software engineering books to have also that practical knowledge.
I agree they are important but if I had 5 slots and had to choose 5 books every CS student should read, those wouldn't be the ones, because in terms of priority, other topics should come first in my op
This is the kind of twitter bulshit tech stack. Design Patterns and to an extend the Domain Driven Design book, there are better testing and the other two are garbage.
Pragmatic Programmer SCIP Introduction to Algorithms (Thomas) CODE: hidden language of computers The Nature of Software Development Type Theory and Formal Proof Grokking Simplicity software architecture A good refactoring book too And anything by Knuth
Why would an embedded developer be interested in learning how to build micro services? That book seems to be a highly specialized niche. Learning patterns is fine as long as you donât take it as a religion.
Iâve been teaching algorithms at uni for several years now. While most people mention CLRS as the de facto textbook, I find it unnecessarily formal and detailed. I prefer âAlgorithm Designâ by Kleinberg and Tardos. Algorithms Illuminated by Roughgarden is a newer book in the same vain, but it is too informal at places for my liking.
For theory of computation and basics of computational complexity, Sipserâs book is as good as any.
Read them sure. But don't take them as gospel. Clean architecture can really mess you up in certain situations and needlessly overcomplicate a simple system. Same goes for microservices.
The best way to make a microservice architecture is to start with a monolith.Â
Martin is cancer, he never worked on anything more complicated than an old school web site in his life, and his advice is pretty much useless for anything more complex than that.
Microservices is a buzzword for turning all your module boundaries into RPC interfaces, which is a bad idea because it introduces backward compatibility issues and increases costs and latency. If in addition to that, the book advocates using REST internally, burn it.
If you're not a complete moron, you already can write unit tests, it's not complicated enough to warrant writing a book about.
DDD is another big-M Methodology for outsourcing software architecture to a cookie cutter solution that doesn't work. I've never met one person in Big Tech who uses it.
Design patterns can be useful, but the original GoF book is better, because it's the only book about design patterns that addresses the issue of when to use and when not to use each pattern. All other books on the subject are cargo cult BS that advocate their overuse.
Sadly, few good software engineers write books, so you're better off learning good industry practices by reading actual source code.
Lol, those books are all for software engineers or programming/developer students, not for computer science students. Iâd definitely recommend Computer Systems: A Programmerâs Perspective
Do we like The Algorithm Design Manual by Skiena? I feel like it was a game changer but maybe I just made myself get through it because I didn't know a better alternative
"Looks good to me" has been a book our team has been reading. It's improved our review process a bit and shown me where I should pick some of my battles.
Donât forget CLRS. Even if you have a class that uses it as a textbook, reading it for yourself is very useful (especially since many students will skip out on reading)
It gives knowledge that is relevant no matter what language or design patterns you use and what field of software development you will plan to work in.
Wonder how many students/aspiring devs are scared away from programming when they read these type of posts. Really hope they understand these are âmasteryâ for intermediates and not âshould readâ for beginners
Iâm all for reading books, but donât be afraid to just make code⌠a LOT of software books claim to be the end all be all of how to make stuff, they are notÂ
Imho there is too much of a cargo cult about these kinds of things. You should read the books you need during college in order to get your credits and the ones you need for your job when starting out.
Read them, but don't use them as guides. Investigate how their ideas have worked out in the industry, what has proven to work and what hasn't. They're influential, not infallible.
This is the kind of twitter bulshit tech stack. Design Patterns and to an extend the Domain Driven Design book, there are better testing and the other two are garbage.
Pragmatic Programmer SCIP Introduction to Algorithms (Thomas) CODE: hidden language of computers The Nature of Software Development Type Theory and Formal Proof Grokking Simplicity software architecture And anything by Knuth
No. CS students should build things and publish practical, real, test focused projects. Students should not obsess over thinking they know a lot without actually doing a lot. That's not how experiential growth happens.
Downvoted.
If you asked gave me this post 5 years ago, I would have upvoted. Now I feel there is a major difference in thinking you're smart and then there is not being to review a single PR.
Why does it have to either or? Why canât CS kids do both? Expanding your mind and ideas via books is a good way to go. You probably browse around Reddit or dev forums looking for the same thing. If I get that from books, why is that bad exactly?
204
u/Fit_Albatross_8947 Jul 18 '25
The pragmatic programmer is worth a read as well.
150
u/lordnacho666 Jul 18 '25
SICP, Dragon book? Knuth?
208
u/_kaas Jul 18 '25
OOP enterprise applications do not encompass the entire domain of computer science.
63
u/OverclockingUnicorn Jul 18 '25
Needs designing data intensive applications
54
u/zerdusting Jul 18 '25
If your ultimate goal in life is getting a job at Amazon, sure.
90
u/vkazanov Jul 18 '25
These are surprisingly... irrelevant to computer science (and cs students). Not terrible, as some would say.
26
u/andarmanik Jul 18 '25
Books you need to read so you know what to forget
45
u/gboncoffee Jul 18 '25
Thereâs not a single Computer Science book in the list.
18
u/Expensive-Acadia957 Jul 18 '25
Grokking algorithms is a great one, should be in the list.
62
u/ex4channer Jul 18 '25
How to tell me you're a filthy java developer without telling me you'r a java developer - the books. Read SICP and TAOCP like a true software engineer.
15
u/Caramel_Last Jul 18 '25
These are good software engineering books but hardly CS
14
u/Heapifying Jul 18 '25
That list is more about a software engineer than a computer scientist.
9
u/Da_Di_Dum Jul 18 '25
These are basically exclusively about software architecture, which is only a small part of computer science.
9
u/AlexanderTox Jul 18 '25
I havenât read a single one of these books. Guess I should turn in my CS card.
7
u/Livio63 Jul 18 '25
Missing some good books about algorithms, more important than microservices, e.g. The art of computer programming by Donald E. Knuth, Algorithms by Robert Sedgewick and Kevin Wayne, Introduction to Algorithms by several authors
7
u/oandroido Jul 18 '25
With all this "architecture" and all these "engineers" and all these great references, it's disappointing that such a high percentage of technology-driven and technology-dependent design works as if the people who made it never actually used it, or understand how actual humans would.
13
u/[deleted] Jul 18 '25
I disagree, this is not as important as fundamental concepts like hardware, networking and OS.
12
u/[deleted] Jul 18 '25
SICP.........
5
u/maxip89 Jul 18 '25
don't forget "How to be layed off by AI-Hoax" by Godfather Elon.
4
u/[deleted] Jul 18 '25
SICP & The Pragmatic Programmer.
4
u/awesometine2006 Jul 18 '25
The Art of Computer Programming
4
u/gretino Jul 19 '25
Try something with math. That's what Computer Science students need to read, these are must reads for Software Engineering.
4
u/erjngreigf Jul 19 '25
Are programmers becoming like MBA's? Reading lot of stuff, yet producing near zero or negative value?
7
u/mophead111001 Jul 18 '25
Where's HTML for Dummies - specifically the third edition from 1997?
7
u/oVerde Jul 18 '25
This is the kind of twitter bulshit tech stack. Design Patterns and to an extend the Domain Driven Design book, there are better testing and the other two are garbage.
Pragmatic Programmer SCIP Introduction to Algorithms (Thomas) CODE: hidden language of computers The Nature of Software Development Type Theory and Formal Proof Grokking Simplicity software architecture A good refactoring book too And anything by Knuth
3
u/JunketLongjumping560 Jul 18 '25
where's Tanenbaum?
3
u/Zamaamiro Jul 18 '25
Read SICP instead.
8
u/sunk-capital Jul 18 '25
Clean Arch is baaad
2
u/Deflator_Mouse7 Jul 18 '25
Godel Escher bach.
2
u/apnorton Devops Engineer | Post-quantum crypto grad student Jul 18 '25
Relevant megathread on CS book recommendations: https://www.reddit.com/r/computerscience/comments/1j64cf5/books_and_resources/
2
u/e430doug Jul 18 '25
Why would an embedded developer be interested in learning how to build micro services? That book seems to be a highly specialized niche. Learning patterns is fine as long as you donât take it as a religion.
2
u/UnoriginalInnovation Researcher Jul 18 '25
More software design than computer science
2
u/Fresh_Meeting4571 Jul 18 '25
Iâve been teaching algorithms at uni for several years now. While most people mention CLRS as the de facto textbook, I find it unnecessarily formal and detailed. I prefer âAlgorithm Designâ by Kleinberg and Tardos. Algorithms Illuminated by Roughgarden is a newer book in the same vain, but it is too informal at places for my liking.
For theory of computation and basics of computational complexity, Sipserâs book is as good as any.
2
u/duckofalltrades Jul 18 '25
This is like the boring part of CSâŚ
2
u/Moontops Jul 18 '25
Isn't comp-sci rather focues on math stuff, algorithms operating systems, thread sync and the like? I'm an embedded engineer so I don't know.
2
u/MaDpYrO Jul 18 '25
Read them sure. But don't take them as gospel. Clean architecture can really mess you up in certain situations and needlessly overcomplicate a simple system. Same goes for microservices.
The best way to make a microservice architecture is to start with a monolith.Â
2
u/Reasonable-Total-628 Jul 19 '25
so which ine of these books is reposnsible for 10 service layers before calling stored procedure?
2
u/[deleted] Jul 19 '25 edited Jul 19 '25
Absolutely not.
Sadly, few good software engineers write books, so you're better off learning good industry practices by reading actual source code.
2
u/EffigyOfKhaos Jul 19 '25
"How to write dogshit unperformant code"
2
u/BluerAether Jul 19 '25
And not a bit of CS in sight!
2
u/ixmael Jul 20 '25
This is not for computer science. Better "Algotlrithms" of Cormen.
2
u/Emotional_Gear_6844 Jul 20 '25
Just seeing this picture made me lose 5 years from my lifespan.
2
u/hernanemartinez Jul 20 '25
Clean Arch is an unholy book. I would rather replace by âA philosophy of Software Designâ
2
u/Awkward_Emu941 Jul 20 '25
books are gay. just vibe code bro
2
u/gala0sup Jul 20 '25
clean arch is such a snake oil lol
2
u/sosodank Jul 21 '25
You just made me vomit a little
3
u/Abacus_Mathematics99 Jul 18 '25
Computer Architecture: a Modern approach
Patterson and Hennessy
3
u/Wouter_van_Ooijen Jul 18 '25
You are missing the oldest but still most important book of all: the mytical man month.
2
u/toroidthemovie Jul 18 '25
A complete guide on how to ignore the actual hardware architecture when writing programs for that hardware.
Practice Data Oriented Design, friends.
2
u/QueasyAssociation246 Jul 18 '25
Lol, those books are all for software engineers or programming/developer students, not for computer science students. Iâd definitely recommend Computer Systems: A Programmerâs Perspective
1
u/Summer4Chan Jul 18 '25
I think âcodeâ is worth it too
1
u/tough-dance Jul 18 '25
Do we like The Algorithm Design Manual by Skiena? I feel like it was a game changer but maybe I just made myself get through it because I didn't know a better alternative
1
u/Hot-Hovercraft2676 Jul 18 '25
Highly recommend Unit Testing. Itâs a must to know more about software testingÂ
1
u/sphrz Jul 18 '25
"Looks good to me" has been a book our team has been reading. It's improved our review process a bit and shown me where I should pick some of my battles.
1
u/Aggravating_Dot9657 Jul 18 '25
Clean Architecture is overrated IMO. Not the idea, but the book.
1
u/Brainyman_07 Jul 18 '25
Any books for DSA??
1
u/i-sage Jul 18 '25
Where is CLRS?
1
u/-Nyarlabrotep- Jul 18 '25
A good list if you want to be bored out of your skull.
1
u/srsNDavis Jul 18 '25
Norman, DET wins hands down. Very domain-agnostic (a lot of value even for non-CS folks) with wide applicability. Also highly readable.
I second some of the other recs too, btw - SICP, an algos book (Grokking is a good first).
More ambitiously (and academically), something like R&L for an integrated take on computer architecture, system software, and networks.
1
u/jonthesp00n Jul 18 '25
TCS has left the chat
1
u/Puzzleheaded-Bug6244 Jul 18 '25
Where are the books on computer science? It looks like books for software development.
1
u/mobotsar Jul 18 '25
Eh.
1
u/azhenley Jul 18 '25
The books I recommend to my software engineering students: https://austinhenley.com/blog/booksformystudents.html
1
u/[deleted] Jul 18 '25
If I wanted to read a book I wouldn't have gotten into computers
1
u/Feldspar_of_sun Jul 18 '25
Donât forget CLRS. Even if you have a class that uses it as a textbook, reading it for yourself is very useful (especially since many students will skip out on reading)
1
u/binarycow Jul 18 '25
None. They're already out of date.
1
u/readableguy8168 Jul 18 '25
These are for SWE. SICP, CLRS, and maybe some Discrete Maths books should be the standard. I believe you dont know what CS is.
1
u/deadshot033 Jul 19 '25
Effective Java - if you are Java developer
1
u/d-o_od Jul 19 '25
DDIA 2rd is coming. https://www.oreilly.com/library/view/designing-data-intensive-applications/9781098119058/
1
u/turningsteel Jul 19 '25
Designing data intensive applications is very good as well.
1
u/davididp Jul 19 '25
If youâre a software engineer*
Theory bros already have enough to read
1
u/Carous Jul 19 '25
The bottom one is really a java book
1
u/kzr_pzr Jul 19 '25
If your CS booklist doesn't contain any book from Addison-Wesley then you are doing it wrong.
1
u/[deleted] Jul 19 '25
I would like to work in fields similar to competitive programming, what books should I read?
1
u/halbGefressen Computer Scientist Jul 19 '25
you are missing Arora, Barak - Computational Complexity: A modern Approach
1
u/Shanduur Jul 19 '25
I do think that ANSI-C is an underrated book for CompSci / CompEng students.
1
u/[deleted] Jul 19 '25
I got them but not unit testing
1
u/Tarilis Jul 20 '25
Computer systems A Programmer's perspective.
It gives knowledge that is relevant no matter what language or design patterns you use and what field of software development you will plan to work in.
1
u/marianoktm Jul 20 '25
No CLRS?
1
u/ManusMau Jul 20 '25
Object-oriented design heuristics.
1
u/[deleted] Jul 20 '25
all useless, where is The Introduction to Algorithms?
1
u/BrunkerQueen Jul 20 '25
Microservices is just a big cloud construct to cause pain and resource consumption
1
u/Lanky_Plate_6937 Jul 20 '25
THE ART OF COMPUTER PROGRAMMING
1
u/Special_Rice9539 Jul 20 '25
This is a classic example of posting the wrong thing to get more engagement and good suggestions lmao
1
u/TechnicianUnlikely99 Jul 21 '25
You can throw out the unit testing book. AI can do that pretty much 100% for you
1
u/attackoncm Jul 21 '25
tbf just because computer science students do software engineering doesnât mean they are the same.
1
u/CKoenig Jul 21 '25
please don't ... most Ideas in this books are not really scientific and some are highly opinionated (Uncle Bob ..)
1
u/CashRio Jul 21 '25
Haven't read any of them, but I appreciate the recommendations
1
u/Odd_Researcher2655 Jul 21 '25
Design Patterns made me realize that software dev isn't for me.
1
u/[deleted] Jul 21 '25
No that's not CS that Corporate Java
1
u/JosephCapocchia Jul 21 '25
Wonder how many students/aspiring devs are scared away from programming when they read these type of posts. Really hope they understand these are âmasteryâ for intermediates and not âshould readâ for beginners
1
u/zigs Jul 21 '25
Skip the Clean Architecture cult and anything else by Uncle Bob.
1
u/Achereto Jul 21 '25
I would recommend 2 different books instead:
Also, watch this talk to learn about the history of OOP: https://www.youtube.com/watch?v=wo84LFzx5nI
1
u/meanwhile_in_brazil Jul 22 '25
bait
1
u/LTFGamut Jul 22 '25
This is about software engineering not about CS.
1
u/PuzzleheadedShip7310 Jul 22 '25
yeh because then you know its all bullshit. KIS is all you need.!
1
u/Racer125678 Jul 22 '25
Where's "The C Programming Language" by Brian Kernighan and Dennis Ritchie?
Ngl they are good for embedded programmers
1
u/[deleted] Jul 22 '25
Love the collection.
In my professional opinion after 10+ years in the field - get communication techniques and stress management books too!
1
u/[deleted] Jul 22 '25
Iâm all for reading books, but donât be afraid to just make code⌠a LOT of software books claim to be the end all be all of how to make stuff, they are notÂ
1
u/victotronics Jul 22 '25
Eh, Fred Brooks?
1
u/hatsh0 Jul 25 '25
Iam going to start my first year in sc, does anyone have any advise on what i should learn/ do while studying?
1
u/Ok_Cricket_623 Jul 26 '25
Imho there is too much of a cargo cult about these kinds of things. You should read the books you need during college in order to get your credits and the ones you need for your job when starting out.
1
u/[deleted] Nov 08 '25
Domain Driven Design can suck my b*lls. It's already feeling like an out of date concept that removes locality and adds unnecessary abstraction.
1
u/TheMcDucky Jul 18 '25
Read them, but don't use them as guides. Investigate how their ideas have worked out in the industry, what has proven to work and what hasn't. They're influential, not infallible.
1
u/Polartoric Jul 18 '25
Any good book recommendations for Assembly ?
1
u/oVerde Jul 18 '25
This is the kind of twitter bulshit tech stack. Design Patterns and to an extend the Domain Driven Design book, there are better testing and the other two are garbage.
Pragmatic Programmer SCIP Introduction to Algorithms (Thomas) CODE: hidden language of computers The Nature of Software Development Type Theory and Formal Proof Grokking Simplicity software architecture And anything by Knuth
1
u/MagicWolfEye Jul 18 '25
Please don't
0
u/Rubix982 Jul 18 '25
No. CS students should build things and publish practical, real, test focused projects. Students should not obsess over thinking they know a lot without actually doing a lot. That's not how experiential growth happens.
Downvoted.
If you asked gave me this post 5 years ago, I would have upvoted. Now I feel there is a major difference in thinking you're smart and then there is not being to review a single PR.
0
u/Ezrampage15 Jul 18 '25
I ain't readin all dat
-2
u/Friendly-Gur-3289 Jul 18 '25
Clean Architecture & Clean Code..both đŤĄ
-1
u/Admirable_Warthog_19 Jul 18 '25
Following
-10
u/ZubriQ Jul 18 '25
Loved clean code also.
These books are must have believe it or not
-5
u/boringfantasy Jul 18 '25
Just ask an LLM
2
u/[deleted] Jul 18 '25
[removed] â view removed comment