Hacker News Reader

When entering and exchanging potentially very large money amounts, it behooves risk management of entered, encoded, and transmitted prices carefully like the following: NDC.

N = Length of string D

D = [0-9]+\.[0-9]+

C = 2 check digits using IBAN method against ND

View on HN

> When the trader checked the value of the inputted basket, they were presented with a figure of negative 58 million for the value of the basket (58 million multiplied by -1). The trader saw a ValAtBM of -58,000,000, which was the number they expected to see, and thus they clicked Execute to continue to the next check.

It wouldn't help.

It doesn't seem that this would have helped here: the trader entered exactly the number that they intended to, just that their intent was misconceived.

Perhaps and perhaps another compounding factor was error-prone UX such as not displaying total estimates prominently or the presence of options leading to order-of-magnitude differences.

But the intent of what I suggested is to guard against many classes of errors including data entry, storage, transmission, and interpretation.

Reply on news.ycombinator.com