• Kusimulkku@lemm.ee
    link
    fedilink
    arrow-up
    0
    ·
    1 day ago

    It’s definitely still concerning if the database has a large number of errors. But systematic fraud would be much worse ofc.

    • funkless_eck@sh.itjust.works
      link
      fedilink
      arrow-up
      0
      ·
      1 day ago

      the database doesn’t have to necessarily be accurate if there’s other checks - a flag for test data, a system that checks the person is real against another database before dispersing funds etc

      • JackbyDev@programming.dev
        link
        fedilink
        English
        arrow-up
        0
        ·
        20 hours ago

        It’s really funny to me that everyone thinks every database is always 100% correct. What a magical world it would be!

        • JcbAzPx@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          23 hours ago

          Fixing an archival dataset that doesn’t even pertain to people actively receiving benefits is so far down the list of priorities as to be a criminal misuse if resources.

        • Lyrl@lemm.ee
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          1 day ago

          Someone with the skills and knowledge to clean up 150-year old typographical errors in one particular table in the Social Security database system would probably provide more benefit to the taxpayers covering their salary by doing some other task.

          • Kusimulkku@lemm.ee
            link
            fedilink
            arrow-up
            0
            ·
            1 day ago

            It might be better to move to a new database at this point rather than trying to fix the existing one. It won’t give immediate benefits but could be helpful down the line.