There are systems that accept writes in multiple places (to the same object). So you could read writes applied in different order on different nodes, though in theory eventually all the nodes will converge on the same object value. This is akin to dirty writes, a consistency level no actual database allows. That’s the distinction between stale and ... eventually consistent.
TL;DR stale and consistent is better than inconsistent.
It's not recommended to get what are called full body scans - one of the main reasons is all the false positives and unnecessary alarms it causes. Most of us have some artifacts that will show up on various scans and will look exactly the same next year and next decade.
On the other hand, many tumors are now discovered incidentally when getting a scan for something else. That tends to also cause higher anxiety levels, but at the same time allows addressing a real issue at a much earlier stage.
To be more accurate though - it used to be a lot worse than it is now. Even as recently as a decade ago the stuff they gave you to drink to clear you out was much more ... what's the word... let's say unpleasant. They now have stuff that is just as effective clearing everything out but without such unpleasant sensations...
That was a result of a bug https://jira.mongodb.org/browse/SERVER-48307 in the retry mechanism when commitTransaction failed to return a response and has been fixed in 4.2.8. Not all databases have memes, I have a high degree of certainty all of them have bugs.
Pre-COVID that was the reality for many. But even post-COVID, certain types of commutes can actually help mentally "separate" the work time from home time. Working at home it's a lot harder to "go to work" and/or "leave work behind" when you "come home".
A friend used to say that majority of people who work from home fall into one of two types of people, the kind that never go to work or the kind that never come home.