Ask HN: What is the best programming book you've read?
1–10 of 56 posts
Re: Ask HN: What is the best programming book you've read?
#2Re: Ask HN: What is the best programming book you've read?
#32. How to Design Programs
3. Software Design for Flexibility: How to Avoid Programming Yourself Into a Corner
Re: Ask HN: What is the best programming book you've read?
#4Because the problem today is complexity and abstractions. It prevents us from changing code easily, deleting code easily, and understanding the full program flow easily.
Re: Ask HN: What is the best programming book you've read?
#5Re: Ask HN: What is the best programming book you've read?
#6If anyone has a good book about writing as simple programs as possible instead of as flexible as possible, I would appriciate it. Because the problem today is complexity and abstractions. It prevents us from changing code easily, deleting code easily, and understanding the full program flow easily.
Re: Ask HN: What is the best programming book you've read?
#7Did not agree with everything but it was excellent.
Re: Ask HN: What is the best programming book you've read?
#8If anyone has a good book about writing as simple programs as possible instead of as flexible as possible, I would appriciate it. Because the problem today is complexity and abstractions. It prevents us from changing code easily, deleting code easily, and understanding the full program flow easily.
Totally agree. Premature abstraction is just another way to say premature optimization and it is the root of so many problems. YAGNI (you aint gonna need it).
Re: Ask HN: What is the best programming book you've read?
#92. Practical Common Lisp
3. A Programmer’s Introduction to Mathematics
4. Data Structures and Programming Design in C
5. The Art of Agent Oriented Modeling
Re: Ask HN: What is the best programming book you've read?
#10All the tips are very focused on how the code, APIs and even the languages evolve, trying to understand how your changes could confuse other developers. Compared to clean code, it's clear that it's written by someone who has done a lot of coding and seen the evolution, with a very pragmatic approach. Not just theoretical like Clean Code