Cannot agree more! Some words just do not have bad connotations in the techie community. Yes they may sound so to the suits, but who cares about the suits? : )
Processor interrupt? Sounds negative. Let’s rename it “request for attention.” This sounds positive. On the same note, halt? Oh boy, what a monster invented that! Let’s rename HLT to RNCD (Rest and Cool Down). Abort? Did someone invent that to subliminally bring politics into programming??? Programs should not abort or crash, they should be “precautionary stopped.”
I’m a linguist, among other things (I’m a SWE and a speech scientist, too), and I am staying as far as I can from the prescriptivism. Our language took hold in the hacker culture of the 60s, it’s nearly 60 years old. Attempting to forcibly PCize a language which have been live for two generations is both futile and will be met with entirely understandable resistance. Language is a living thing, and resists such a rough treatment.
Diplomats talk in a professional code that non-diplomats do not understand—why words that seem soft and neutral if not friendly actually mean the harshest hair trigger warning possible? Marketing people talk in a slang I’m not even trying to grok. And we the SWE also have own abstand language. “In which version of Emacs was this function added?”—“I do not remember, I think it was 23, but go blame it.” Nobody blames anyone here. And we also recognize our fellow guildsmen by it; societal identity is also tied to the language in a very important way!
A common element in techie’s¹ speech is its directness, and this is not only remarkable from the descriptive vantage point, but also has its direct effect on the end result. If engineers were talking to each other about mistakes, inconsistencies or flaws in roundabout hints instead of straightforward truth, the things that they build would more likely blow up on liftoff, or break down and flood a city, or crash down into a river with 200 cars and buses on it, or abort and freeze a bank or, in our epidemic time, unemployment payment service, or mess up scientific data collection. The more direct we are to each other (and we understand that ‘git blame’ is no more about blame than git(1) is a git), the better working contraptions we build (and this is the utmost reward for us!), and in the better world we end up.
¹ Thirty years ago I would say “hacker”, but the word has shifted its connotation, or perhaps even changed its semantic. It changed by itself: nobody wrote a blog post to change it, there was no movement for it, no proposals, no consensus (although, of course, some discontent among the graybeards that any language change causes). Language is a living thing, and it’s very easy to overestimate how much power we have over it: in fact, very little to none.