That would create much more chaos, because every region autonomously decides on its timezone(s). You'd have different countries and/or timezones using different leap second counts.
It may be good enough to make me more productive, but only because I don’t relent on ensuring that the code is well-reasoned. Indeed, I don’t experience that when I do relent.
I don’t think that the logical reasoning ability of LLMs depends on the abstraction level. Their heuristic knowledge differs between levels, but that’s a different thing. My concern is the reasoning capabilities.
What’s interesting to me is reasoning about the problem and its implementation. And that doesn’t stop at any abstraction level. Reasoning in the small is just as important as reasoning in the large. And the issue with LLMs is that their capacity for sound reasoning is limited. They are sloppy on any level. You can’t get them to be thorough and dependable in reasoning, regardless of the abstraction level.
It decreases legibility by breaking the norms of written communication. That makes it distracting and annoying to read, and makes me want to not engage with it. It’s like talking to someone face-to-face who smells because they chose to not bathe for a week. They might have something worthwhile to say, but it’s difficult to ignore the form being a strong turn-off.
The N100 supports "In-band ECC" (IBECC), which uses regular non-ECC RAM at the cost of less available memory and a 10-20% performance drop. It’s unclear how well it works, and almost nobody uses it.
DDR5 on-die ECC is to achieve acceptable yields in the face of denser process nodes that decrease the reliability of RAM cells. It’s not clear how much of an improvement that is to what we had before, other than allowing for higher RAM speeds. It doesn’t replace side-band ECC.
This isn’t black and white. You might have huge amounts of non-essential data that aren’t worth the cost of off-site backups, but worth the cost of an extra disk of redundancy to lessen the risk. Even when you do have backups, it will reduce the risk of extended downtime (and possibly egress costs) caused by having to restore large amounts of data from backups.