Ask HN: Good books on philosophy of engineering?
Engineers and software developers trade recommendations for books that explore the deeper philosophy of engineering, from system safety and design simplicity to the nature of quality, professionalism, and technological ethics. Suggestions range from classics like "The Art of Doing Science and Engineering," "Zen and the Art of Motorcycle Maintenance," and "The Design of Everyday Things" to critical works on technology’s social impact and essays on how engineers think and work. A recurring theme is that engineering is not just applied science or coding, but a way of seeing the world, managing complexity, and balancing human values with technical constraints.
General engineering philosophy & history
- Many recommend narrative or reflective books on engineering failures, structures, and large projects (bridges, Apollo, nuclear submarines, aircraft, atomic bomb) as ways to understand responsibility, iteration, and “why things don’t fall down.”
- Several highlight works explicitly about “what engineering is,” its history, and how engineers think, including short overviews and more academic treatments of “what engineers know and how they know it.”
- Case-study–driven books are valued for showing that practice often precedes theory and that useful engineering can happen without full scientific understanding.
Software, computing, and design
- Strong support for books that frame software as design and problem decomposition: “A Philosophy of Software Design,” “The Art of Unix Programming,” “The Art of Computer Programming,” SICP, and texts on generic programming and Scheme.
- Opinions are mixed on popular “clean code”/OO books: some find them foundational and perspective-shifting; others feel they’re dogmatic or overrated but still acknowledge their influence.
- Several emphasize design/UX-focused texts on everyday objects, naming, and interface simplicity as philosophically important for engineers.
Systems, complexity, and failure
- Recommended works on systems thinking, accidents, and “how complex systems fail,” plus satirical or practical “systems bibles,” are seen as crucial for understanding limits of large systems and the importance of incremental, simple designs.
- Papers like “A city is not a tree” and classic essays on committees, research, and humility in programming are cited as must-reads.
Critical and ethical perspectives
- A sizeable subthread promotes critical philosophy of technology: critiques of “solutionism,” instrumental reason, imperialism of tools, and the social/political dimensions of artifacts.
- Works on information and computer ethics, technology as practice (not neutral tools), and “convivial” tools are recommended as counterbalance to triumphalist engineering narratives.
Spiritual, existential, and Eastern-influenced angles
- Books like “Zen and the Art of Motorcycle Maintenance,” Tao Te Ching, Zen teachings, and psychological/spiritual texts are repeatedly suggested as ways to think about quality, debugging, simplicity, and one’s relationship to work.
- These draw both enthusiasm (for their treatment of quality, mindset, debugging, and “propensity/flow”) and skepticism (accusations of shallowness, boredom, or irrelevance in an engineering context), with some saying such works “land” only at certain life stages.
Craft, culture, and work life
- Memoirs and essays on craftsmanship, blue-collar vs “knowledge work,” shop class, and workplace management are praised for exploring meaning, satisfaction, and the “soul” of engineering work.
- Several posters stress that philosophy of engineering is inseparable from organizational culture, risk, and human factors, pointing to talks and newsletters as complementary resources.