Typographic jacket · original cover not fetched
FROM THE SHARED SHELF · 2006–2026 SAMPLE
Topics are model-inferred labels.
THE WORD OF MOUTH
Original Hacker News comments, in the readers’ own words.
2 books I consider excellent: - A Philosophy of Software Design by John Ousterhout - Domain-driven Design: Tackling Complexity in the Heart of Software by Eric Evans They both manage to explain some ideas that are really important, in a very simple way (which makes me feel like an idiot).
Also recommended in this reply
Elicitating the real needs of customers is the most challenging part for me within a software development process. The concept of Domain Driven Design (book by Eric Evan) helped me a lot to decode the language of the customer and transform it into an object model.
Domain Driven Design: https://smile.amazon.com/Domain-Driven-Design-Tackling-Compl... (https://smile.amazon.com/Domain-Driven-Design-Tackling-Complexity-Software/dp/0321125215) It's not about designing APIs, it's about designing your software to reflect the reality you're encoding into your software. It's a book of first principles that you can apply to any software you design.
You make a fair point but I think it raises a more general question that has come up before plenty of times and that is whether classical computer science is good training for 95% of students. Take civil engineers. Yes they will do some physics but usually only basic stuff in first year. After that they focus more on the higher level systems they will be working with because most working civil engineers will never need anything more advanced than first year physics. So if the person who posted this Ask HN is not going to do CS research (or the like) then Domain Driven Design might be as fundamental to their education as structural engineering is to a civil engineer. The fact is that nearly all systems that we work with are composed of services/models of some kind. DDD deals with these but more importantly deals with the domain where you can make the most impact as a working engineer (as opposed to a scientist who is like a force multiplier but we need a lot less of them).…
Refactoring by Martin Fowler and Kent Beck. Patterns of Enterprise Application Architecture by Martin Fowler. Domain Driven Design by Eric Evans. Growing Object-Oriented Software, guided by tests by Steve Freeman and Nat Pryce.
Also recommended in this reply
There were different book that impacted different stages of my career: As a programmer : 1. The C++ Programming Language by Bjarne Stroustrup. 2. Operating System Concepts by Silberschatz 3. Compilers by Aho As an agile software developer: 1. eXtreme Programming by Kent Beck 2. Pragmatic Programmer by Hunt and Thomas 3. Continuous Delivery by Jez Humble As an architect: 1. Domain Driven Design by Evans 2. Pattern-Oriented Software Architecture by Buschmann 3. Envisioning Information by Edward Tufte As a CEO: 1. Good To Great by Collins 2. Lean Startup by Eric Ries 3. Beyond Budgeting by Pfläging
Also recommended in this reply
Domain Driven Design by Eric Evans.
Eric Evans' "Domain-Driven Design: Tackling Complexity in the Heart of Software" blew my mind. Domain modeling gets to the heart of object-oriented programming. The book is a bit academic and long-winded, but very deep and complete. This is an immediate classic and required reading for any serious engineer.