What's the best way to minimize the need of run time checks?

[BartC]

On 10/08/2016 02:47, Steven D'Aprano wrote:
> On Wed, 10 Aug 2016 11:02 am, Chris Angelico wrote:
>
>> On Wed, Aug 10, 2016 at 10:58 AM, Juan Pablo Romero Méndez
>> <jpablo.romero at gmail.com> wrote:
>
>>> This is interesting. You are Ok having runtime errors?
>>
>> Absolutely. In real terms, there's no difference between "compile-time
>> error" and "run-time error that you trigger the moment you run your
>> program".
>
> That's an oversimplification.
>
> How about the difference between getting a compile-time error immediately
> you try to compile your program, and a run-time error three quarters of the
> way through processing a billion records, leaving your data in a corrupted
> state?

And when it is a customer (perhaps in a different country) who is in the 
middle of running your code.

> I love the fact that the computer on the Apollo lunar landers was expected
> to have bugs, and was designed to automatically reboot and continue the
> calculation that was interrupted. By memory, it rebooted something like 30
> or 40 times during the first moon landing.

Wouldn't the same error just recur each time? Or was this a random 
hardware error rather than logic?

-- 
Bartc