Thanks for the recommendation! It’s very rare to see book recommendations on the Forum, which is odd considering the goals and methods of EA (we should be reading a lot of books).
In the past, books I’ve read that collect “common lessons of successful projects” have usually run into the problem of picking out successful anecdotes after the fact, and ignoring cases where the book’s chosen rules/phenomena applied equally well to various projects that failed. (In the case of this book, that might equate to ignoring cases where a crazy idea is rejected for a long time, then accepted, only for it to become clear that it should have stayed rejected.) Do you think the author avoids this issue?
Agree about books. I’d say the main ways that I differ in my approach came from reading a ton of books in specific areas which, besides just the straightforward skill-up, also made me less correlated with others’ approaches thus increasing the potential for consilience.
Thanks for the recommendation! It’s very rare to see book recommendations on the Forum, which is odd considering the goals and methods of EA (we should be reading a lot of books).
In the past, books I’ve read that collect “common lessons of successful projects” have usually run into the problem of picking out successful anecdotes after the fact, and ignoring cases where the book’s chosen rules/phenomena applied equally well to various projects that failed. (In the case of this book, that might equate to ignoring cases where a crazy idea is rejected for a long time, then accepted, only for it to become clear that it should have stayed rejected.) Do you think the author avoids this issue?
Agree about books. I’d say the main ways that I differ in my approach came from reading a ton of books in specific areas which, besides just the straightforward skill-up, also made me less correlated with others’ approaches thus increasing the potential for consilience.