I'm starting to notice this alot now and not sure if this is just hanlon's razor or actual malice (im going with the latter).
at some point a timestamp is converted. a backend likely changed. the new backend had a different timestamp format, something like that. it was different.
different is bad. it needed to go back to looking like the rest. it needed to be “4 days ago.”
from the back of the zoom call, a lone voice said “hang on, sharing my screen, it can be done in a few minutes…”
it was a backend engineer.
no one said stop. (narrator: someone should have said stop.)
so, now, instead of anything close to an iso timestamp, you get an approximate relative date.
there might even be a ticket to fix it. but it isn’t broken. so it isn’t priority, and it never will be…