Meme transcription:

Panel 1: Bilbo Baggins ponders, “After all… why should I care about the difference between int and String?

Panel 2: Bilbo Baggins is revealed to be an API developer. He continues, “JSON is always String, anyways…”

  • andyburke@fedia.io
    0·
    2 days ago

    You are a fintech dev using floating point? And your advice is to encode things as strings?

    …

    This is why I got out of fintech.

    (I am sorry, I know there are horrors and I am sure I am not familiar with your exact scenario.)

    Edit: just for anyone who passes by: try to stick with integers in a currency’s smallest unit of division. (This is only one small bit of this problem, but the number of times I have seen currency values in floating point makea me psychotic.)

    • bleistift2@sopuli.xyzOPEnglish
      0·
      1 day ago

      try to stick with integers in a currency’s smallest unit of division

      And then the marketing department comes up with products that cost 1.5ct apiece.

    • Scrubbles@poptalk.scrubbles.techEnglish
      0·
      2 days ago

      Until you get to multi currency, which is why I don’t support using ints or longs, and strings are still the only way. There are currencies that have no precision, and others that have 3 or more digits of precision - and then you’re looking at doing calculations each time. Strings are the safest way to make sure you’re representing exactly what you want to when sending data over the wire or persisting