Ask HN: What's the best book you've read regarding software development?

Perplexity:

Based on the discussions from the provided Hacker News threads, here is a list of ten notable books recommended by users, particularly in the context of software engineering and programming:

## Top Ten Recommended Books

- *The Pragmatic Programmer* by Andrew Hunt and David Thomas A classic in software development, this book offers practical advice and principles for programmers.

- *Clean Code: A Handbook of Agile Software Craftsmanship* by Robert C. Martin This book emphasizes writing clean, maintainable code and has become a staple in programming literature.

- *A Philosophy of Software Design* by John Ousterhout This book provides insights into software design principles and the importance of simplicity in design.

- *Domain-Driven Design: Tackling Complexity in the Heart of Software* by Eric Evans A foundational text for understanding complex software systems and how to manage them effectively.

- *Designing Data-Intensive Applications* by Martin Kleppmann This book covers the principles of designing applications that handle large volumes of data efficiently.

- *Refactoring: Improving the Design of Existing Code* by Martin Fowler Focuses on the process of refactoring code to improve its structure without changing its functionality.

- *Code Complete: A Practical Handbook of Software Construction* by Steve McConnell This comprehensive guide covers best practices in software construction and coding techniques.

- *Effective Java* by Joshua Bloch A must-read for Java developers, this book provides best practices for writing robust Java code.

- *The Mythical Man-Month: Essays on Software Engineering* by Frederick P. Brooks Jr. A classic work discussing the complexities and challenges of managing software projects.

- *Programming Pearls* by Jon Bentley This book presents programming problems and solutions that enhance problem-solving skills and algorithmic thinking.

These books are highly regarded within the programming community and cover a range of topics from coding practices to software design philosophies, making them valuable resources for both new and experienced developers.

Citations: [1] https://news.ycombinator.com/item?id=41387062 [2] https://news.ycombinator.com/item?id=35929112 [3] https://news.ycombinator.com/item?id=32130578 [4] https://news.ycombinator.com/item?id=41387062 [5] https://news.ycombinator.com/item?id=35929112 [6] https://news.ycombinator.com/item?id=32130578 [7] https://news.ycombinator.com/item?id=29498220 [8] https://news.ycombinator.com/item?id=29306651

Even the second edition is over twenty years old. I don't think there's any reason not to read the second edition.

np. The 2nd edition, have not read the 1st :-)

On the personal interest level? It kind of snowballed. I was 13 when I finally saved up enough allowance money to purchase copies of Minecraft for my sister and I. I can not understate how sad I was when I couldn't find any emerald items, nukes, or clay soldiers to make civilizations for in my creative inventory. This was where I learnt all of those were mods, and not in the base game. I was too young to understand how to use forge (let alone make my own mods), so I got into adventure maps and minigames using command blocks and redstone. I made friends and we worked on each other's stuff. I panned out to have a knack for the command block side of it while others could utilize building skills to make the levels pretty and well designed. It was a lot of fun. When I started taking programming classes in high school and found out the command block work translated over to me doing well with coding, it was pretty set in stone that game programming was what I wanted to go into. I went to a well-ranked college with it as an available major.

> heard horror stories about what the industry is like now...

There definitely are. You have to remember to value yourself and who you are outside of your work, or else you can be taken advantage of. If the amount of work you're doing is so much that you can't do the other things that make you "you," it's too much work.

I graduated at the same time this never-ending wave of layoffs began, so it has been stressful at many points. Some of my best friends have been a part of those lay offs. Some of us pivoted to a new career because there wasn't a chance to even get started. I made do for some time by going to indie game developer events in the city my family lived near. I built relationships, found in-person community, and landed enough contract work as a Unity programmer to pay my student loans until I could find something long-term.

I now work at a small company where we do a mix of Unity and Web development. Sometimes it's our own products/services, but until those are successful enough we do contract work regularly to build out our runway. I enjoy what I do at work a whole lot, and it's been great getting critique from senior programmers with loads more experience than me. Very thankful about where I am.

In the future, I think I'd be okay with changing over to something else in SWE for my career, so long as it was to help people. I know that I love working with others on games enough that I'd still do it in my free time, just like I did when I was "mapmaking" as a kid.

what specifically about it if you don't mind me asking?

if i remember correctly Esther is no different than cinderella or any other rags to riches fairy tale story

if a poor person gets powerful allies they become powerful else they die not a paradigm altering POV tbh