No, it's Excel trying to be too clever. It does the same thing with manual imput if you don't proactively change the field type.
You can import a DSV into Excel without mangling datatypes in a few different ways. Probably the best way is using Power Query.
A DSV generally does have a schema. It's just not in the file format itself. Just because it isn't self-describing doesn't mean it isn't described. It just means the schema is communicated outside of the data interchange.
As we know from THERAC-25, etc., comprehensively verifying that code works the way it's expected to is not actually very easy - it's perhaps one of the hardest parts of building any system more complex than a toaster.
Worth noting that you've slipped from "checking whether something works is easy" to "well, it's probably not as harmful as a very notable failure if it fucks up."
It sounds like Blacksky's outage was much more limited and was caused by them missing some spots where their code still accidentally had some Bluesky integration due to it being the default: https://bsky.app/profile/rude1.blacksky.team/post/3mjnf6pubr...
Xinput is a pretty constrained interface that plenty of novel controllers, including steering wheels, don't/can't adhere to. Good luck getting the PS5 controller's fancy rumble working over xinput, for example
reply