It seems that any technology loves to spawn acronyms and, at times, it can all seem like alphabet soup. Sometimes acronyms evolve from being an acronym to being the name of something. For example, I spent many years thinking that JDBC was an acronym for Java Data Base Connectivity. Now, however, knowledgable folks, including the authors of the Sun JDBC API Tutorial, tell us that JDBC is not an acronym for anything. It’s the name of an API.
I’m OK with JDBC being the name of an API but I like to pronounce it by saying each letter: J-D-B-C. This makes sense to me even if it isn’t an acronym.
What has been making my head spin lately is a growing trend to “pronounce” acronyms as words. JNDI (Java Naming and Directory Interface) is the acronym for the naming API specified by JEE (Java Extended Edition). I pronounce it J-N-D-I. Several weeks ago I was talking with a technology instructor who kept pronouncing it Gin-Dee. I had to ask him what Gin-Dee meant which probably didn’t do much to bloster my stock in his view. But I had never heard J-N-D-I called Gin-Dee before.
Since that time I have noticed this trend more and more:
- SOA pronounced Sew-Ahh
- URL pronounced Earl
- JEE pronounced Gee
I am starting to become concerned that one day I will no longer understand my colleagues when they speak to me.
“The Earl for the Sew-Ahh service will be stored in the Gee Gin-Dee tree”.