I don't think that's the case. It's very possible to be a good programmer and care deeply about your work, but at the same time be a terrible UX designer. Unfortunately a lot of software companies don't realize this and give UX the priority it deserves; instead they make their coders guess about it, which leads to things like this dialog.

Oh sure, I'm a living disaster area at UX. I meant more that whoever is the "designated responsible individual" (if one even exists -- doubtful) has given the fuck up.

For some reason I didn’t read “the fuck” as emphasis, but as a direct object—the person had had a fuck previously, but have since given up that fuck.

I’m going to use that as an example of why UX is hard: not only are people generally not paying attention, but sometimes they misfire even when they are.

It's much more elegant in your reading.

The basics of UX design can be learned, so if you really care you'll learn.

Or, the error message was written by someone whose first language is not English... and the company in question did not enforce review.

or even that the message makes perfet sense to the person writing it, because they are not reading the message, but reading what they thought the message was in their head!

Or maybe the backend code is analogous to

    bool exit_handler(obj) {
        return confirm_exit(obj->description)
    }

and he simply missed the unfortunate dialog box that resulted in one of those cases. An oversight, but when the subtitles of the user presentation is so decoupled from the code it can be easy to miss.