So I asked this same question to ChatGPT, here's its response. This thing really does have the potential to be a good recommendation tool for books/resources. "Here are a few books that may be helpful for improving your skills as a software engineer: "The Pragmatic Programmer" by Andrew Hunt and David Thomas: This book offers practical advice on a wide range of topics, including how to write clean and maintainable co…
This answer scares me. Wow
Ask HN: Reading material on how to be a better software engineer?
71–80 of 134 posts
Re: Ask HN: Reading material on how to be a better software engineer?
#72So I asked this same question to ChatGPT, here's its response. This thing really does have the potential to be a good recommendation tool for books/resources. "Here are a few books that may be helpful for improving your skills as a software engineer: "The Pragmatic Programmer" by Andrew Hunt and David Thomas: This book offers practical advice on a wide range of topics, including how to write clean and maintainable co…
This answer scares me. Wow
Re: Ask HN: Reading material on how to be a better software engineer?
#73Earlier quoted context omitted.
Robert C. Martin has ruined so many mid organizations it's kind of funny
Having never read Clean Code, why do you say that?
As someone who also recommends against improving developers reading Clean Code, I think the arguments in that piece are generally on point.
Re: Ask HN: Reading material on how to be a better software engineer?
#74I have all of these on my shelf. Fantastic reads. * Extreme Programming Explained by Kent Beck * Clean Code and The Clean Coder by Robert C. Martin * Soft Skills by John Sonmez (1st edition) * Pragmatic Programmer by Andrew Hunt and David Thomas * Working Effectively with Legacy Code by Michael Feathers * The Mythical Man-Month by Frederick Brooks (Selfish plug) Additionally, I wrote my own book concerning the entire…
Re: Ask HN: Reading material on how to be a better software engineer?
#75A Philosophy of Software Design by John Ousterhout is good reading
Re: Ask HN: Reading material on how to be a better software engineer?
#76That's a bit like "Ask HN: Reading material on how to be a better pianist?"
You will need to write and maintain a lot of code, and make a lot of mistakes, then you will get gradually better.
Re: Ask HN: Reading material on how to be a better software engineer?
#77Re: Ask HN: Reading material on how to be a better software engineer?
#78I'd consider these books/articles/podcasts:
* Secrets of Consulting by Gerald Weinberg: http://geraldmweinberg.com/Site/Consulting_Secrets.html Every problem is a people problem.
* Refactoring by Martin Fowler et. al: https://martinfowler.com/books/refactoring.html talks about how and why to refactor, as well as providing a nomenclature for the process.
* Code Complete by Steve McConnell. https://stevemcconnell.com/books/ A bit dated (the last version I could find was from 2004) but a great overview of the entire software process, from requirements to maintenance.
* The Mythical Man-Month by Fred Brookes: https://www.oreilly.com/library/view/mythical-man-month-the/... best practices about software development, written about a project from the 1960 and 1970s.
* The Joel On Software Strategy Letters: https://www.joelonsoftware.com/2000/05/12/strategy-letter-i-... is the first one. All of them (I think there are five) are great.
* Letters to a New Developer: https://letterstoanewdeveloper.com/the-book/ Please note I wrote this, but I still think it does a good job of discussing the "soft skills" in an easily digestible format.
* Pragmatic Programmer by Dave Thomas and Andy Hunt: https://pragprog.com/titles/tpp20/the-pragmatic-programmer-2... Haven't read the revised 20th anniversary edition, but the first one opened my eyes to the craft of software.
* High Output Management by Andy Grove: https://bookshop.org/p/books/high-output-management-andrew-s... a great way to think about throughput
* The Phoenix Project by Gene Kim et. al: https://itrevolution.com/product/the-phoenix-project/ Fun novel(!) about applying lean management principles to software engineering.
* Radical Candor (haven't read, but it's been recommended): https://www.radicalcandor.com/ About communication.
* Good to Great by Jim Collins: https://en.wikipedia.org/wiki/Good_to_Great Focuses on what great companies bring to the table. Helps me evaluate where to work.
* Mastery Autonomy and Purpose: A great video about what people really want in work: https://www.youtube.com/watch?v=MzXXC4MZZnY
* https://www.manager-tools.com/podcasts a podcast about managing people. You didn't say you wanted to be a people manager, but knowing what managers think about will make you more effective in any org.
* Managing Humans by Michael Lopp: https://managinghumans.com/ The whole Rands site is work reading, but I enjoyed this book about how to manage teams and build software. See above.
* Don't Make Me Think by Steve Krug: https://sensible.com/dont-make-me-think/ Easy ways to think about usability, focusing on webapps. Short and easy.
* Badass: Making Users Awesome, by Kathy Sierra: http://seriouspony.com/badass-users-the-book Will help you put yourself in the shoes of your users and think about how to build software they will love. Short and easy.
Hope this helps.
Re: Ask HN: Reading material on how to be a better software engineer?
#79Re: Ask HN: Reading material on how to be a better software engineer?
#80OP, I've been thinking about starting a column on those kinds of lines - generalized engineering advice. I have 20+ years of experience in the industry and have held both principal engineer and engineering director positions at S&P 500s. Does that hold your interest? For everyone else, I think I've created an interesting backlog of topics, but I'd love any advice about additional topics that would interest folks, how…
What are your goals? Just to get your stuff read, help other folks be better engineers, to build a consulting business, to build a recruiting pipeline, something else?
Your goal affects any advice I'd give.