This is a log output message. The problem with logs is that they are first and primarily written for the developer. I'm writing the alert for the condition I need to know about. It's only as an afterthought that they are revised to be read by not-developer and bear some semblance of communicating an event or status. This is why most logs, especially the debug kinds, are inscrutable. Devs may eventually put in logs for other people, but unless thought is put into who will consume the log and what the expected actions would be, the original logging text remains.
The human who wrote the automated text was probably coding toward identifying vacancy. Aha! Vacancy detected! What's more natural than coding that into the alert message? That person is probably not thinking about the death of a student, a less frequent event than graduating, moving, whatever.
I get what the author is trying for, there are actually heartless automatic messages involving actual death or traumatic events. This is not those. I'm not thinking about how to not inadvertently hurt someone's feelings when I'm writing logs, it's first written in a very confined objective for me.
The human who wrote the automated text was probably coding toward identifying vacancy. Aha! Vacancy detected! What's more natural than coding that into the alert message? That person is probably not thinking about the death of a student, a less frequent event than graduating, moving, whatever.
I get what the author is trying for, there are actually heartless automatic messages involving actual death or traumatic events. This is not those. I'm not thinking about how to not inadvertently hurt someone's feelings when I'm writing logs, it's first written in a very confined objective for me.