From 6c03b259e8f5b67475eab95252fb887933ddd509 Mon Sep 17 00:00:00 2001 From: Kate Hudson Date: Tue, 22 Jul 2014 16:47:10 -0400 Subject: [PATCH] what are flight rules --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index 4baf91e..e0ef06a 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,14 @@ # Flight rules for git +## What are "flight rules"? + +> *Flight Rules* are the hard-earned body of knowledge recorded in manuals that list, step-by-step, what to do if X occurs, and why. Essentially, they are extremely detailed, scenario-specific standard operating procedures. [...] + +> NASA has been capturing our missteps, disasters and solutions since the early 1960s, when Mercury-era ground teams first started gathering "lessons learned" into a compendium that now lists thousands of problematic sitautions, from engine failure to busted hatch handles to computer glitches, and their solutions. + +— Chris Hadfield, *An Astronaut's Guide to Life*. + + ## Conventions for this document For clarity's sake all examples in this document use customized bash prompt in order to indicate the current branch and whether or not there are staged changes. The branch is enclosed in brackets, and a `*` next to the branch name indicates staged changes.