3 ms·
It is how you talk about failure when it is another part of your engineering characteristics and not something that causes fear or shame. Another reminder is w
by colechristensen 8y ago
It is how you talk about failure when it is another part of your engineering characteristics and not something that causes fear or shame.
Another reminder is why you run tests. They don't scare away failure by existing, they are there to catch failure, doing their jobs exactly as intended.
It will probably result in a delay of any human spaceflight by SpaceX until the source of the source of the problem is removed. (not the particular issue that caused the anomaly but the systematic issue which didn't find it before it happened on the pad)
- Dylan16807 8y ago> It is how you talk about failure when it is another part of your engineering characteristics and not something that causes fear or shame. That depends on whether this was supposed to be the final test. If it's a post-hoc "final", then that's an obfuscation done out of shame. If it was always supposed to be the final test, then the statement is fine.
- HeyLaughingBoy 8y agoIt really doesn't matter if it's the final test or not. Your QA (or dev, or whatever) group has a number of test cases to verify. They verify the ones that they can, and record failures against the ones that they couldn't not. Sometimes in hardware testing, a failed test results in destruction of the hardware and/or peripheral damage to the test environment. BTDT.
- Dylan16807 8y agoI'd expect riskier tests to go later, so the implications are worse the earlier in the sequence it breaks.
- HeyLaughingBoy 8y agoIME, riskier tests are run later, because you want as much test feedback as possible so the tests that aren't likely to break something are run first. However, you can't really draw any conclusions from that unless you know what the test plan was.
- perl4ever 8y agoWhen did an "unscheduled disassembly" become an "anomaly"??