…. or maybe not so noble,
but more a tactical assault on the problem.
- Slap some stuff together
- Understand what you did, what it does, and what it should do.
 If you don’t or it doesn’t, revert to 1…
- Fix the remains so it does what it was supposed to do,
 in a passable fashion.
- Run it by some innocent victim (aka guinea pig or co-worker),
 and see about their reaction.
 If bad, revert to step 3.
- Prettify, if required…(trust me, it is.)
- Do a QA / code review with your peers (guinea pigs),
 and when the number of Whiskey Tango Foxtrots/minute
 goes below 1, you are generally safe to proceed.
- Release the product.
- Duck/Hide under the table, wait for the client fallout and bugs to be reported.
