• JcbAzPx@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      17 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
      9
      arrow-down
      1
      ·
      edit-2
      20 hours 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.

      • AA5B@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        11 hours ago

        How would you clean up that data? If they didn’t have the correct data in the first place, where do you expect to find it decades later?

        Sometime real life is just bad data and that’s not necessarily a problem. All of the business logic and agency process around not spending money for those situations is probably one of the difficult areas blocking modernization or shrinkage. Bad data is reality. How you handle it shows how experienced you are

      • Kusimulkku@lemm.ee
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        19 hours 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.