There's nothing wrong with making mistakes in experiments. However, when you're building financial systems, there's absolutely no room for mistakes.

Most financial systems are designed to have room for mistakes.

Banks keep ledgers of transactions instead of just the balances, so that if an account balance is off, it can be recalculated from the transactions.

Transactions can be cancelled in case there was an error.

Invoices are often checked by humans before they are sent to customers, introducing an option to catch errors. If the customer receives a faulty invoice, they can contact whoever wrote it and ask for a correction. And so on.

Of course, there isn't room for error in every corner -- having a flaw in an authentication or authorization protocol could be very costly to recover from.

But in general, the assumption that in finance in general, there is no room for mistakes is simply false.

There is always room for mistakes if you start by building prototypes. In fact having first approximation prototypes allows one to catch mistakes in how systems and subsystems interact early and fix those at a fraction of the cost.

Developing on a live fintech system is a different kettle of fish

> However, when you're building financial systems, there's absolutely no room for mistakes

Then I can assume that all of your financial software has verification proofs and/or is fully model checked? If not, then clearly there is room for mistakes even in finance.