Great list. One I always think about is “To engineer is human” by Henry Petroski. It’s about sudden catastrophic failures in large engineering projects like bridges or building structures. Generally architecture and civil engineering are overused analogies in computer engineering however this book made me think more about failure, the importance of failures in producing better design and my overall approach to defensive software development. It’s an older book but I read it only in the last few years and I think it is timeless.
Others that might interest you is Midnight in Chernobyl and how the Soviet beauracracy really screwed up. Another good book is called "The Adolescense of P-1"
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great list. One I always think about is “To engineer is human” by Henry Petroski. It’s about sudden catastrophic failures in large engineering projects like bridges or building structures. Generally architecture and civil engineering are overused analogies in computer engineering however this book made me think more about failure, the importance of failures in producing better design and my overall approach to defensive software development. It’s an older book but I read it only in the last few years and I think it is timeless.
Others that might interest you is Midnight in Chernobyl and how the Soviet beauracracy really screwed up. Another good book is called "The Adolescense of P-1"