> meaning CBP personnel would have to manually untangle the amounts. Processing each individual refund takes about 5 minutes, which across 53 million entries works out to over 4.4 million hours.
Assuming nobody looks at the requirements of the problem to write a single line of code in order to tool up to the task.
Many lifetimes ago I worked on a project where all customer desired changes were 'scoped' by engineering. A little report was written about how the change could be implemented, to include any possible complications and a LOC estimate.
My manager, did not want us to do a customer desired change. So he wrote the 'impact report'.
The problem basically required taking functionality that applied to 1 thing, and made it apply to an (existing) array of things. His solution was as if arrays did not exist, and the resulting LOC was N times bigger than it actually was going to be.
Of course, this change was not authorized until the manager left, and someone that knew it was BS spoke up.
Same thing here.
> CBP’s Automated Commercial Environment (ACE) system can apparently only batch-process 10,000 entry summary lines at a time, and there are over 1.6 billion entry summary lines that need updating. Importers frequently lumped their IEEPA duties together with other duties on the same line, meaning CBP personnel would have to manually untangle the amounts. Processing each individual refund takes about 5 minutes, which across 53 million entries works out to over 4.4 million hours.
While ridiculous, from a technical standpoint, it's not hard to see how this scenario arises. On the one hand, there was probably pressure to implement the tariffs as quickly as possible. Consequently, there likely wasn't much effort put into the "what if we have to undo all this in a year" use case, because that wasn't strictly necessary to get the tariffs implemented.
On the other hand, now that the "we need to undo all this" use case actually needs to be used, they've gotta go back and solve the problem after the fact. Unsurprisingly, it's going to take a while to develop that solution.
I'm not excusing it, but I do think it's interesting to think about the technical and political issues.
Well Trump's track record of "No Plan-B" has historically worked out for him pretty well so far. He had ample reason to think the SCOTUS--which has been giving him a green light to act like a god-king up to this point--would have his back on this as well, in which case who cares if his backup plan turned out to be complete rubbish?
When there is no financial data to steal or person to randomly fire, suddenly there is not anymore 20 years old DOGE morons pretending to be able to fix the system overnight...
Claiming it takes 5 minutes of manual work per entry while also saying it would take 45 days to build a software solution is a strange contradiction. In any private sector logistics setup, if you have 53 million records to untangle, you don't even consider the manual route; you spend the first 30 days building the parser and the next 15 days running edge-case tests. The fact that they are even presenting the '4.4 million hours' figure as a viable metric for the court shows how disconnected the administrative process is from modern data engineering.
12 comments
[ 52.3 ms ] story [ 100 ms ] threadAssuming nobody looks at the requirements of the problem to write a single line of code in order to tool up to the task.
On the other hand, now that the "we need to undo all this" use case actually needs to be used, they've gotta go back and solve the problem after the fact. Unsurprisingly, it's going to take a while to develop that solution.
I'm not excusing it, but I do think it's interesting to think about the technical and political issues.