JayUtah
Penultimate Amazing
This reminds me of the unholy mess that is date/time stamp data in NSSDC telemetry. However, for someone like Musk who pretends to be a galaxy brain to immediately jump to the "fraud" conclusion when he encounters something he doesn't understand is entirely irresponsible. Anyone who has had to work in legacy systems knows about epoch problems in offset-encoded dates and/or times.It's not actually a COBOL thing.
Whoever wrote the code, that just how they chose to do it. COBOL has standard Y2K compliant dates as well.
Epochs are always arbitrary. For spacecraft, the epoch is often the launch date. The practice of reckoning years from the accession of a monarch persisted well into the 21st century, if only for ceremonial purposes.20 years since I wrote COBOL so I checked my copy of COBOL Unleashed - they mention the CYYDDD format "uses the year 1990 as a starting point (or any other years that you choose)". So the 1875 appears arbitrary.
Similarly, when it's important to include the concept of "unknown value," you want an explicit pattern of bits to represent that, so you can distinguish between garbled data and legitimately missing, unknown, or computationally invalid data (such as the result of dividing by zero). And you want that to be a clearly "wrong" value, which doesn't preclude it being arbitrary. And it often can't be zero. And you would do this even if you switched to a purportedly epoch-less format such as YYYYMMDD. (The Gregorian calendar just uses the accepted birth year of Jesus as its epoch.) If the designers and users of a system used a specific date well in the past to encode the idea of, "We don't know the actual date," then anyone who was actually familiar with the system would soon learn to recognize 18750520 as "no known date."
The point is only slightly tarnished by other people's mistaken efforts to attribute this to some inherent feature of COBOL. It's also hasty and wrong, but it's a wholly minor order of error compared to jumping from, "Hm, what's going on here?" to saying under color of law, "Someone must be committing fraud!" Unfortunately it feeds the myth that anyone who criticizes Elon Musk's intellect doesn't know what they're talking about.
You can lament the existence of legacy systems and you can decry a policy that doesn't update them regularly. But there's no excuse for turning them over to techno-toddlers to break while "fixing" them. I think some people already pointed out Musk's complaint that some databases weren't "de-duped" to remove "duplicate" Social Security numbers. This is more properly interpreted as Musk's ignorance of the practice of leaving some databases unnormalized because they run faster that way. Experience matters. So does honesty.