DEV Community

Cover image for Killed by Acronyms
Felix Coutinho
Felix Coutinho

Posted on Edited on

Killed by Acronyms

Speaking the same language doesn't mean understanding each other.

If English isn't your first language and you've worked in tech, chances are you've been attacked by acronyms at least once.

I certainly have.

They're everywhere. Meetings, emails, documentation, architecture diagrams, and those lovely onboarding presentations where someone somehow manages to squeeze fifteen acronyms into a single slide.

And the funny thing is, most of us just pretend we understand. Not because we understand everything, but because nobody wants to be the person who interrupts a meeting to ask what yet another three-letter abbreviation means.

At least, that's what I used to think.

My First Encounter With the Acronym Jungle

I'm not exactly an Elon Musk fan, but I remember coming across an internal SpaceX memo he sent back in 2010. In it, he complained about the excessive use of acronyms, calling them a major source of communication problems.

For once, I found myself agreeing with him.

My own experience was slightly less exciting than building rockets.

It was my first day at my first job abroad. Everything was new: the country, the workplace, the people, and, of course, the language.

The day was packed with onboarding sessions. HR, Security, IT, and a few departments I didn't even know existed.

Every presenter seemed to speak a different dialect of corporate English. I could understand the words, but the acronyms? Not so much.

I remember sitting there trying to decode one acronym while the presenter had already moved on to three others.

But somewhere around the third meeting, I noticed something interesting.

The native English speakers weren't doing much better.

I could see the same confusion on their faces. They were just better at pretending they understood.

That's when something clicked for me.

I had assumed my difficulty with acronyms was another challenge of working in a second language. But the problem wasn't really English.

It was the assumption that everyone in the room already knew what everyone else was talking about.

And that's a much bigger communication problem.

When Shortcuts Make Things Slower

One concept I keep coming back to in software engineering is Cognitive Load.

We normally discuss it in relation to code complexity, system design, or developer experience. But I think it applies just as much to how we communicate.

Acronyms are supposed to make communication easier. And sometimes they do.

If everyone in a conversation knows what an acronym means, using it is perfectly reasonable. It saves time, avoids repetition, and keeps things moving.

The trouble starts when that shared understanding doesn't exist.

Imagine joining a meeting and hearing:

"Can we run an RCA to understand why the MTTR is increasing in our ITSM process?"

If you've spent years working in IT operations, you probably understand that sentence immediately.

If you haven't, good luck.

You're now trying to figure out what RCA means, what MTTR means, and why ITSM is part of the conversation. By the time you've connected the dots, someone is already explaining the proposed solution.

You haven't missed the conversation because you weren't paying attention.

You've missed it because you were busy translating it.

That's the hidden cost of acronyms. They save a few seconds for the speaker but can cost everyone else considerably more time and mental effort.

As architects, we spend a ridiculous amount of time trying to reduce unnecessary complexity in our systems.

Why should our communication be any different?

English Is Already Hard Enough

There's another aspect of this problem that I don't think gets enough attention, especially in international teams.

English has become the default language of technology, whether we like it or not.

For someone who grew up speaking English, expressions like FYI, ASAP, ETA, or EOD might be second nature.

For someone who learned English later in life, they're an additional vocabulary layer that isn't always taught in language classes.

And unlike regular words, acronyms are especially dependent on context.

Take ETA, for example. Once you know it means "Estimated Time of Arrival," it's simple enough. But until you learn it, those three letters don't tell you much.

Now multiply that by the dozens of abbreviations used across departments, companies, and technical domains.

It's not necessarily that non-native speakers understand less. Often, they're doing more work to understand the same conversation.

I've experienced this myself, and it's exhausting when it happens repeatedly throughout the day.

Of course, native speakers aren't immune either. Move someone from Finance into Engineering, or from Development into Infrastructure, and suddenly they may feel like they're learning a new language.

Which brings me to something else.

Acronyms and the Illusion of Expertise

Every company seems to have its own collection of acronyms that nobody remembers inventing.

Some are useful. Others have survived for years simply because "that's what we've always called it."

Eventually, they become part of the company's tribal knowledge.

People who've been around long enough understand them. Newcomers are expected to figure them out.

And asking for clarification can feel uncomfortable, particularly when everyone else appears to know what's going on.

I suspect we've all been in a meeting where we didn't understand an acronym but decided to Google it afterward rather than interrupt.

I've done it.

The ironic thing is that I've also seen senior people admit, much later, that they had no idea what the acronym meant either.

Sometimes, I even wonder whether people use so many acronyms because they genuinely improve communication or because they make the conversation sound more sophisticated.

After all, saying "We need to optimize the MTTR based on the RCA findings" somehow sounds more impressive than saying "We need to reduce recovery time based on what we learned from the incident."

But sounding technical and communicating effectively are two different things.

And I'd rather work with someone who explains a complex subject clearly than someone who makes a simple subject sound complicated.

What Domain-Driven Design Taught Me About Communication

As a Software Architect, I tend to look at these situations through the lens of system design.

One of the ideas I appreciate most in Domain-Driven Design (DDD) is the concept of Ubiquitous Language.

The principle is straightforward: developers, architects, and domain experts should share a common vocabulary when talking about the business and its systems.

Not three different names for the same concept. Not a collection of mysterious abbreviations that only one team understands.

A shared language.

And excessive acronyms can work directly against that principle.

Consider something as simple as ATM.

In banking, it usually means Automated Teller Machine.

In networking, it can mean Asynchronous Transfer Mode.

Same acronym. Completely different concepts.

Now picture an architecture diagram with two boxes labeled PVS and ODS, connected by a few arrows.

What exactly am I looking at?

Is PVS a Payment Validation Service? A Provisioning System? Something entirely different?

Unless I'm familiar with that specific organization, I have no idea.

And if I need to schedule a meeting with the diagram's author just to understand what the boxes represent, something has gone wrong.

Architecture diagrams are supposed to help people understand systems.

They're not supposed to be puzzles.

A good diagram should provide enough context for someone to make sense of it without having its author standing next to them.

That's especially important when documentation is shared across teams or handed to people who weren't involved in the original design.

So, Should We Stop Using Acronyms?

Not at all.

I'm not advocating for eliminating acronyms. That would be impractical, especially in technology.

Try having a conversation about APIs, HTTP, SQL, or JSON without using abbreviations. It would get old pretty quickly.

The point isn't to avoid every acronym. It's to be more intentional about using them.

A few habits can make a noticeable difference.

1. Don't assume everyone knows your acronym.

There's a difference between widely recognized technical terminology and something invented by your department five years ago.

Even common technical acronyms aren't universally understood, but internal ones are particularly risky.

If you're speaking to people outside your immediate team, a little extra context goes a long way.

2. Explain it the first time.

This is probably the simplest improvement we can make.

Instead of writing:

"We need to improve MTTR."

Write:

"We need to improve Mean Time to Recovery (MTTR)."

That's it.

You've spent a few extra seconds writing, and everyone reading now has a better chance of following the discussion.

If the acronym appears frequently afterward, go ahead and use it. At least people know what it means.

3. Make your architecture diagrams readable.

This one is particularly close to my heart.

If you're designing a diagram, give components meaningful names.

And if the full name doesn't fit inside a box, make the box bigger.

Seriously.

Nobody is going to award you points for fitting an entire distributed system into a beautiful diagram that nobody understands.

I'd take a slightly ugly but clear architecture diagram over a visually impressive collection of mysterious three-letter boxes any day.

One Last Thought

I've worked with people from different countries, technical backgrounds, and levels of experience. One thing I've learned is that speaking the same language doesn't automatically mean we're communicating well.

Acronyms are a perfect example.

They can be incredibly useful when everyone shares the same context. But when that context is missing, they turn something simple into unnecessary work.

And the worst part is that we often don't realize it's happening.

The person speaking thinks they've been perfectly clear. The people listening don't want to admit they're confused. Everyone leaves the meeting believing they're aligned.

Until they're not.

One simple practice I've always liked is maintaining an Acronym Dictionary for a team or department. Nothing fancy. Just a shared, searchable document explaining the abbreviations people actually use.

Make it available to newcomers, encourage everyone to contribute, and keep it updated.

It won't solve every communication problem, but it can remove one completely unnecessary barrier.

In the end, good communication isn't about how quickly we can deliver information.

It's about whether the person on the other side actually understands it.

And if explaining an acronym takes five seconds but saves someone five minutes of confusion, I think that's a pretty good trade.

Top comments (0)