[swiftcoder]

I think that it is pretty important to both be prescriptive about the pronunciation of abbreviations you create, and to explain them if they are non-obvious.

Way back when I first read about nginx, I had absolutely no way to know that folks usually pronounced it "engine-X". Led to an embarrassing conversation where I and a coworker were completely at cross-purposes to one another.

Obviously there are a bunch of abbreviations with disputed pronunciations (gif/jif, SQL/sequel, etc), and since the creators weren't prescriptive about them, we're all free to argue about them for the rest of time...

[wruza]

Important embarrassing why? In my experience it’s only really important to insufferable people who care about their in-groupness before anything else.

[swiftcoder]

Important because precise communication matters in engineering. I don't mean "embarrassing" in the sense of an in-group, I mean it in the sense that misunderstandings cause engineering mixups that are trivially avoided by clear communication