Article

Newsroom

The Naming Problem: Why We Spend More Time Arguing Than Coding

A recent post by @robertl on MEMBO sparked a conversation about the two hard problems in computer science—and why naming things might be the hardest. Here's why we obsess over names, how it slows us down, and what we can do about it.

naming
software development
team collaboration
productivity
startup

You know that feeling when you've just spent three hours in a naming debate and you realize you haven't written a single line of code? Yeah, me too. It's a special kind of hell.

The Two Hard Problems (and the Third One That's Also a Joke)

There's an old joke in computer science: there are only two hard problems—cache invalidation and naming things. And off-by-one errors. I know, that's three. That's the joke. But as @robertl pointed out in a recent MEMBO post, it's also a prophecy, and we're all living in it.

I felt that in my bones. Just last week, I watched a team spend an entire sprint debating whether to call a feature a "workspace" or a "team." Meanwhile, the codebase already had four different names for it: workspace, team, group, and org_unit. None of them matched the database schema. It was a mess.

Why Naming Is So Darn Hard

Naming is hard because it's not just about picking a word. It's about capturing a concept, setting expectations, and creating a mental model that everyone can share. And when you're building software, those names stick around. They become part of your API, your UI, your documentation, and your users' vocabulary.

I remember early in my career, I named a variable data. Just data. My senior dev looked at it and said, "That's like naming your dog 'Dog'." He was right. But at the time, I was just trying to get the thing to compile. Fast forward six months, and that data variable had spawned a dozen similarly named children: data2, newData, finalData, dataFinalForReal. It was a nightmare to untangle.

But there's a deeper reason naming is hard: it forces you to think. When you name something, you're defining its boundaries, its responsibilities, its relationships. And that's exactly why it's so valuable—and so painful.

The Cost of Naming Debates

Let's be honest: naming debates can be a huge time sink. I've seen teams spend days arguing over button labels. I've seen pull requests stall because someone insisted on isEnabled instead of enabled. And I've seen engineers get genuinely angry about it.

But here's the thing: those debates are often a symptom of unclear thinking. If we can't agree on a name, it's usually because we haven't agreed on what the thing actually is. The name is just the visible tip of the iceberg.

So what do we do? We can't just skip naming (though sometimes I wish we could). But we can get better at it.

How to Get Better at Naming (Without Losing Your Mind)

1. Agree on the concept first, then the name

Before you start throwing out names, make sure everyone understands what the thing does. Write a one-sentence description. If you can't agree on that, you're not ready to name it.

2. Look for existing vocabulary

Does your product already have a term for this concept? Reuse it. Consistency is more important than creativity. Users don't care if your names are clever; they care if they're predictable.

3. Timebox the debate

Give yourself a deadline. If you can't decide in 30 minutes, pick the least bad option and move on. You can always rename later (though, let's be real, you probably won't).

4. Write it down

Keep a glossary. I'm serious. A simple doc that says "we call this a 'workspace' and here's what it means" can save hours of future confusion. At MEMBO, I've seen builders share their glossaries and it's a game-changer for collaboration.

5. Accept imperfection

No name is perfect. The goal is not to find the perfect name; it's to find a name that's good enough and move on. Remember: the code that ships is better than the code that's perfectly named but never sees the light of day.

The Takeaway

Naming will always be hard. It's part of the job. But we can make it less painful by treating it as a design activity, not a linguistic debate. And next time you find yourself in a naming argument, remember @robertl's post—and maybe just pick a name and move on. Your future self (and your team) will thank you.

What's the worst naming decision you've ever made? I'd love to hear about it. (Seriously, I need to know I'm not alone.)

Keep reading the newsroom

Back to all articles