Category: General Development

…. or maybe not so noble, but more a tactical assault on the problem.

1. Slap some stuff together
2. Understand what you did, what it does, and what it should do. If you don’t or it doesn’t, revert to 1…
3. Fix the remains so it does what it was supposed to do in a passable fashion.
4. Run it by some innocent victim (aka guinea pig or co-worker), and see about their reaction.
   If bad, revert to step 3.
5. Prettify, if required…(trust me, it is.)
6. 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.
7. Release the product.
8. Duck/Hide under the table, wait for the client fallout and bugs to be reported.

This shows the importance of fundamental testing of code in Dev and Staging, BEFORE pushing to prod,
no matter the urgency, unless you are absolutely sure it will work and it is an emergency, or, of course,
you are out of options and ready to take the risk of burning down the house…

What could possibly go wrong, right?