3 ms·

I was somewhat worried about that until I saw this: https://twitter.com/nickjshearer/status/1409902649625956361?s=21 https://twitter.com/nickjshearer/status/140

I was somewhat worried about that until I saw this: https://twitter.com/nickjshearer/status/1409902649625956361?s=21 https://twitter.com/nickjshearer/status/1409902649625956361?... I think programming is one of the many domains (including driving) that will never be totally solved by AI unless/until it's full AGI. The long tail of contextual understanding and messy edge-cases is intractable otherwise. Will that happen one day? Maybe. Will some kinds of labor get fully automated before then? Probably. But I think the overall time-scale is longer than it seems.

sillysaurusx 5y ago
64-bit floats should be fine; I think that tweet is only sort-of correct. The problem with floats-storing-money is (a) you have to know how many digits of precision you want (e.g. cents, dollars, a tenth of a cent), and (b) you need to watch out if you're adding values together. Even if certain values can't be represented exactly, that's ok, because you'd want to round to two decimal places before doing anything. Is there a monetary value that you can't represent with a 64-bit float? E.g. some specific example where quantization ends up throwing off the value by at least 1/100th of whatever currency you're using?
- fredros 5y ago
  Storing money as float is always a bad decision. Source: been working for several banks and faced many of such bugs.
  - astrange 5y ago
    Pretty common in financial modeling, which I'm told is all done in Excel.