- p.7 bus factor:
- p.9 interrupt protocol:
- p.14 The moral is this: do not underestimate the power of playing the social game. It's not about tricking or manipulating people; it's about creating relationships to get things done, and relationships always outlast projects.
- p.17 your self-worth shouldn't be connected to the code you write. To repeat ourselves: you are not your code. Say that over and over. you are not your code.
- p.18 Failure is viewed as a golden opportunity to learn and improve for the next go-around.
- p.19 "not hiding in the cave until it's perfect"
The key to learning from your mistakes is to document your failures. Write up "postmortems,' as they're often called in our business. (what was learned and what is going to change)
Don't erase your tracks, light them up like a runway for those who follow you! A good postmortem should include the following: A brief summary, timeline of event, primary cause, impact and damage assessment, a set of action items to fix the problem immediately, a set of action items to prevent the event from happening again, lesson learned.
- p.47 Comments should be focused on why the code is doing what it's doing, not what the code is doing.
