|
| 1 | +--- |
| 2 | +layout: writeup |
| 3 | +title: "Better: A Surgeon's Notes On Performance" |
| 4 | +categories: |
| 5 | +- writeup |
| 6 | +--- |
| 7 | + |
| 8 | + |
| 9 | +[Better: A Surgeon's Notes on Performance][link] |
| 10 | +Atul Gawande |
| 11 | +ISBN: 0805082115 |
| 12 | + |
| 13 | +--- |
| 14 | + |
| 15 | +**What's the point?** |
| 16 | +How can you improve when the cost of failure is so high? Medicine is filled with high |
| 17 | +risk decisions where the consequences of making the wrong choice can result in the loss |
| 18 | +of human life. |
| 19 | + |
| 20 | +While the stakes in developing software are rarely as dire, we can apply |
| 21 | +lessons from medicine to improve our own processes and abilities. |
| 22 | + |
| 23 | +**How was it?** |
| 24 | +At first glance, it is easy to dismiss this book and say that software is nothing like |
| 25 | +medicine. But both professions have to deal with complexity, imperfect information, |
| 26 | +communicating with "clients", and the challenges of working with teams. |
| 27 | + |
| 28 | +As I read the book, it was surprising how many parallel connections I could make to |
| 29 | +software. |
| 30 | + |
| 31 | +Battlefield surgeons perform "patch job" operations and then transfer wounded |
| 32 | +soldiers back to hospitals to receive more care. The surgeons used data to identify |
| 33 | +patterns of injuries and optimized their care. In software, we have hot-fixes and |
| 34 | +track application errors to predict bug reports. |
| 35 | + |
| 36 | +Obstetricians came up with a metric (the [Apgar Score][as]) that provided immediate |
| 37 | +feedback about the condition of a newborn child and allowed for objective comparison. |
| 38 | +Remind anyone else of the recent industry trends of validated learning and metric driven |
| 39 | +development? |
| 40 | + |
| 41 | +[as]: http://en.wikipedia.org/wiki/Apgar_score |
| 42 | + |
| 43 | +My favorite part of the book was the concept of "positive deviance". |
| 44 | + |
| 45 | +Gawande describes how some performers are able to consistently ride the upper tails of |
| 46 | +the bell curve by identifying and maximizing small changes that result in positive |
| 47 | +outcomes. |
| 48 | + |
| 49 | +Being 99.5% effective vs 99.95% effective doesn't seem to make a difference in a day |
| 50 | +— but tally that 0.45% difference up over a year the difference is 83% vs 16%. |
| 51 | +A very powerful example of gradual improvement if you ask me. |
| 52 | + |
| 53 | +**Who should read it?** |
| 54 | +There are good lessons for every developer in this book. Before you reach for the next |
| 55 | +software book about improvement, performance, or team dynamics give this |
| 56 | +cross-disciplinary book a shot; I think you'll be glad you did. |
| 57 | + |
| 58 | +[link]: http://www.amazon.com/Better-A-Surgeons-Notes-Performance/dp/0805082115 |
0 commit comments