Lastly, there's a "game" you can buy through Steam - called GTGD (Gamer to Game Developer) - some Aussie walks through creating a first person shooter with teams and multiple weapons. There's a S1 and S2 and after about 12 or so of the videos (out of 20+ in S1) I had enough to start programming my own game. He's writing it all in c# and explains the code decently.
Or is all fair in war?
But what if the cost to fix the failure is deemed to high? It is an acceptable engineering practice to just plan on something going wrong x% of the time. Now if 1/9 is the maximum failure rate, and you can still get to orbit (meaning you design in the possibility of an engine exploding - can you imagine!), and the probability of 2/9 is astronomical, is something that is "forseen" have to be mitigated? Now granted, I hope the engine failure is truly something anomalous, given that even the smallest fracture can cause problems, and you have to test the engine at least once before use...
Will space travel ever enter the "good enough" phase of manufacturing? Being an A.E. I applaud the design of the falcon engine system. Just like most large aircraft can land with 1 out of 4 engines being functional, a system that can take a full system failure on one of its parts and still perform is quality engineering.
Of course a baked in analytics service for all apps, that could be disabled, would be pretty cool too... Maybe an android level API?
"I have five dollars for each of you." -- Bernhard Goetz