The Software Craftsman
by Sandro Mancuso · first published 2014
75% recommend25% neutral
Why HN recommends it
Covers professional habits and craft for software developers, including career choices, code quality and keeping work in perspective; recommended for programmers aiming to grow professionally.
Summarised by Claude from recommending comments
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
Mentions per year
What Hacker News says
Related books
2008–2026Clean Code
Robert C. Martin
Recommended by 298 · mentioned by 739298 recommend · 739 mention298 recommend · 739298 recommend
2007–2026Refactoring
Martin Fowler
Recommended by 94 · mentioned by 14594 recommend · 145 mention94 recommend · 14594 recommend
2007–2026Code Complete
Steve McConnell
Recommended by 393 · mentioned by 669393 recommend · 669 mention393 recommend · 669393 recommend
2007–2026The Pragmatic Programmer
Andy Hunt, Dave Thomas
Recommended by 353 · mentioned by 589353 recommend · 589 mention353 recommend · 589353 recommend
…Kill a Mockingbird" by Harper Lee. The only nover on the list. Definitely a good read. 4. "The Pragmatic Programmer". I fell in love with the idea of "the network" of views and controllers. 5. "The Software Craftsman" by Sandro Mancuso. Great one. Made me recosinder a few (quite a few!) things in my workflow and project. 6. "Deep Work" by Cal Newport. Amazing one. Can't wait for Monday to implement some at work.…
on “Ask HN: Which book(s) did you read this summer?” ↗This year I read "Clean Coder" by Robert Martin and "The Software Craftsman: Professionalism, Pragmatism, Pride" by Sandro Mancuso. They were both excellent and I recommend them to any programmer who wants to improve his or her Engineering professionalism and craft. Don't be…
on “Ask HN: Books you read in 2018?” ↗I would advice you to read Software Craftsman by Sandro Mancuso. In one of the chapters he explains that enjoyment of life is really essential. We live in times where "rat race" is so prevalent we forget to take a step back and think about "what…
on “Living and working in Sweden as engineers” ↗I would advice reading "Software Craftsman" by Sandro Mancuso. It contains a chapter about hiring "craftsmen" (best kind of developers). And many things from the article check out in regards to that.
on “When hiring senior engineers, you’re not buying, you’re selling” ↗…I started to care about my code more after I read that book. You cannot sit and review each commit, the best you can do is to make them care about code. [1] http://www.amazon.com/Clean-Code-Handbook-Software-Craftsman...
on “Ask HN: How do I get my team to write better code?” ↗…management/leadership role. It's good experience and the "right career move" but it's not what I wanted at this time. Anyone wanting a programming career should read "Apprenticeship Patterns: Guidance for the Aspiring Software Craftsman".
on “Programming Is Not Fun” ↗…wanted to say – that self-explanatory code, and sometimes tests, is almost always better than comments. I just want to point out a good reference on this topic: the book Clean Code: A Handbook of Agile Software Craftsmanship [1], specifically Chapter 4, “Comments”. That chapter gives examples showing which comments should be turned into code and which are acceptable to leave as comments, and it explains the reasoning…
on “The Most Important Code Isn't Code” ↗…understood simply by reading it. Anything complicated I comment, but usually that means I need to refactor and rethink my approach. I highly recommend this book: http://www.amazon.com/Clean-Code-Handbook-Software-Craftsman... as it changed my life when it comes to software development. I have a real problem with commenting everywhere as most of the time you'll find a lot of public String getName() with like a comment of…
on “Does anyone use comments any more?” ↗…such as "Code Complete"[1] and "Clean Code"[2] should help you with that transition. [1] http://www.amazon.com/Code-Complete-Practical-Handbook-Const... [2] http://www.amazon.com/Clean-Code-Handbook-Software-Craftsman...
on “Ask HN:working with a company with anal coding standards” ↗For writing clean code, I highly recommend Uncle Bob's "Clean Code": http://www.amazon.com/Clean-Code-Handbook-Software-Craftsman...
on “What every computer science major should know (2011)” ↗…Clean Code [2], I feel that there is much missing that can lend itself to better code. [1] http://www.oracle.com/technetwork/java/javase/documentation/... [2] http://www.amazon.com/Clean-Code-Handbook-Software-Craftsman...
on “Google's updated Java coding guidelines” ↗…story, at least for me. I guess you just learn by watching old guys do what they do after decades of experience...unless someone has a magic book for me? (1) http://www.amazon.com/Clean-Code-Handbook-Software-Craftsman... (2) http://www.amazon.com/Refactoring-Improving-Existing-Addison...
on “Organizing complexity is the most important skill in software development” ↗The article I Have A Dirty Secret. I'm a Software Craftsman. is making the rounds elsewhere right now. https://levelup.gitconnected.com/i-have-a-dirty-secret-im-a-... https://news.ycombinator.com/item?id=35678278 This feels like a very closely related topic.…
on ““Craft at scale” is a white whale” ↗