Comment by jghn
2 days ago
If something costs more to fix than it costs to leave sitting around, fixing it is less efficient. In this case it's already been investigated prior to DOGE, and deemed not worth the effort to clean up [1].
2 days ago
If something costs more to fix than it costs to leave sitting around, fixing it is less efficient. In this case it's already been investigated prior to DOGE, and deemed not worth the effort to clean up [1].
You fix the system not because of the cost today but because the cost it will eventually cause.
Poor record keeping and bad policies about data validation tied to sending money to people if not today will eventually result in massive fraud.
Furthermore the notion you put forth is trash lazy thinking. Cost or no cost you do things the right way. But I don’t even buy you can calculate the cost of doing it wrong correctly to even have a sound conjecture that fixing it is more costly.
Your point is also covered in the audit report linked by the parent.
Cost was not the only factor. They seem to be trying to handle missing data the right way rather than use a kludge.
They did not want to add inaccurate death data to Numident records, for a variety of reasons, one being that it could cause release of information for living people when they're accidentally added to dead people records. The SSA also thought adding annotations would legally require a new regulation and would have impacts on other consumers of the data (ie. states, etc).
How to handle missing death data in this case does not appear to have a clear and simple solution. But it also does not appear to be evidence of poor record keeping for modern records or a major cause of concern for "eventual massive fraud".
Missing data means == no payments until data is updated.
This creates a driver, somebody who is motivated to get it fixed. If the person does not exist they won’t be calling for their check, or if the entry fraudulent, fraudster will run the risk of exposing them self in the process of trying to get the checks flowing again.
But what if the right way is judging the pros and cons of perfection and doing what makes the most sense?
I think the problem they should be considering more acutely is, eventually the number of people trained in that specialized knowledge will go to 0, and they will then be paying the cost to either train more (and the increased risks of less familiar people) or replace the whole thing with no backup plan.
Given the age of the COBOL programmers I know, that window is rapidly shrinking...
OIG Response: