21–30 of 62 posts
I also enjoyed the green "Dragon Book" [1] on compilers, by Aho and Ullman. I think it must have been thirty years ago, or more, though. [1] https://www.amazon.com/Principles-Compiler-Addison-Wesley-in...
Design Patterns: Elements of Reusable Object-Oriented Software by the Gang of Four.
most colleges student don’t really understand when to use each pattern after reading the book.
I also enjoyed the green "Dragon Book" [1] on compilers, by Aho and Ullman. I think it must have been thirty years ago, or more, though. [1] https://www.amazon.com/Principles-Compiler-Addison-Wesley-in...
agreed! reading this book at a 11 years old completely changed the way i use data structure and write code today.
Thanks for sharing your experience!
You might be familiar with Feynman's Lectures on Physics, but his lectures on Computation (based on a class he taught and his work in 'Connection Machine') aren't any less amazing. Through this short book, Feynman guides us through the concept of computation and the van Neumann architecture in his unique style, from logic functions, to Turing machines, coding and even quantum computers. It will give you a unique appreciation of the finer points in which computers are "Dumb as hell but go like mad" so that you can better squeeze every bit of performance out of your code.
Knuth's "art of Computer Programming", especially and specifically for the way it communicates things. I'm quite weak when it comes to reading advanced maths, but the code communicated to me, and taught me most of what i ever learned about how to read the weird squiggles.
This book is recommended (and heavily upvoted) on every such thread about good software books but I would very much doubt more than 5% have read more than a few chapters, probably less than 1% have read one book in the series and probably less than 0.1% have read the entire series. This is one of those series that everyone thinks they should read but few actually do.
Knuth's "art of Computer Programming", especially and specifically for the way it communicates things. I'm quite weak when it comes to reading advanced maths, but the code communicated to me, and taught me most of what i ever learned about how to read the weird squiggles.
This book is recommended (and heavily upvoted) on every such thread about good software books but I would very much doubt more than 5% have read more than a few chapters, probably less than 1% have read one book in the series and probably less than 0.1% have read the entire series. This is one of those series that everyone thinks they should read but few actually do.
You can make the same arguments about "do people really read their Bibles?" and the answer is it don't matter: if there's any benefit to be had from the book at all, it's much more likely to accrue if you have a copy.
Knuth's "art of Computer Programming", especially and specifically for the way it communicates things. I'm quite weak when it comes to reading advanced maths, but the code communicated to me, and taught me most of what i ever learned about how to read the weird squiggles.
This book is recommended (and heavily upvoted) on every such thread about good software books but I would very much doubt more than 5% have read more than a few chapters, probably less than 1% have read one book in the series and probably less than 0.1% have read the entire series. This is one of those series that everyone thinks they should read but few actually do.
Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems Book by Martin Kleppmann
Design Patterns: Elements of Reusable Object-Oriented Software by the Gang of Four.
while it’s the reference on design pattern it’s still the worse book on the subject. most colleges student don’t really understand when to use each pattern after reading the book.