Let me give you an example that actually happened. We had a rocketship emoji to indicate success in an potentially dangerous operation related to high voltage wires. Right before we made a final release (which we would do every 4 months or so) someone in the QA department brought up that having a rocketship emoji on something that can catch fire and potentially explode is not a very good idea.
This was during a meeting and that derailed the meeting by a few minutes or so, but we had to make new last-minute pre-release for testing to remove the emoji. This was right before a release so pressure was high, you only have to run into something like this a few times before you start to think that this kind of thing is not worth any "good feelings" it might bring.
This job was a high stress environment where we were always behind schedule. This kind of thing, happened often enough that it was really getting to my nerves.
Personally I don't really mind emojis in the software I use as long as it works as intended. What I mind is wasting my time with this kind of stuff. This HTTP 418 is in the same kind of situation, I have had 3rd-party APIs throw 418 back at me (presumably some fun a dev had at that company) and I couldn't even tell if my request was wrong or if that was supposed to be a 500. Software for controlling high voltage is not supposed to be fun, network protocols are not supposed to be fun.
This was during a meeting and that derailed the meeting by a few minutes or so, but we had to make new last-minute pre-release for testing to remove the emoji. This was right before a release so pressure was high, you only have to run into something like this a few times before you start to think that this kind of thing is not worth any "good feelings" it might bring.
This job was a high stress environment where we were always behind schedule. This kind of thing, happened often enough that it was really getting to my nerves.
Personally I don't really mind emojis in the software I use as long as it works as intended. What I mind is wasting my time with this kind of stuff. This HTTP 418 is in the same kind of situation, I have had 3rd-party APIs throw 418 back at me (presumably some fun a dev had at that company) and I couldn't even tell if my request was wrong or if that was supposed to be a 500. Software for controlling high voltage is not supposed to be fun, network protocols are not supposed to be fun.