God wouldn’t say NO to the Pope…
Sure you do.
God wouldn’t say NO to the Pope…
Sure you do.
If you're going to mock a religion it would be best to know something about it next time.
Once again proof that there is no difference between Trump and Biden.
Jesus Christ... 🤦♂️
You think he set the state on fire so he'd be able to ask for disaster relief?
He'll just fire those who don't reply. It's a "power move" not a legitimate management technique.
The president can do whatever the rest of government lets him do.
"would you support me in a coup? Your fired."
Adhesives can be incredibly strong.
He's not. But everyone has to do what he says. Though he's not an employee. Unless it's inconvenient in which case he is.
It's used in mainframes mostly. I don't know COBOL well but I've worked with COBOL systems in the past. I didn't think it even has a "date type" (at least in older systems? maybe it was added at some point?). They just store dates as 8 digits (6 back in the day which led to infamous "y2k" problems). That's why I didn't think they had an epoch. In more modern systems a date is typically "the number of milliseconds since the epoch". For Linux that's 01/01/1970. Either way this explanation for Musk's error is pretty sus. I'm sure he's misunderstanding something (he didn't think the US government used SQL ffs) though.
Edit: It's possible this particular team used that date as some sort of special value. That would be pretty common in older programming styles. But it doesn't seem like it's any sort of "standard."
I thought truth mattered right?
...right?
I was intrigued by this article as 1865 isn't any epoch I've heard about and I didn't think COBOL really had a concept of an epoch (an epoch matters when you're counting milliseconds from zero, COBOL stores date/time info differently). I've been searching this morning and can only find the Wikipedia page mentioning that date - which is weird for an ISO standard that is 99% about date formatting.
No.