UX Collective

We believe designers are thinkers as much as they are makers. https://linktr.ee/uxc

Follow publication

Member-only story

Why “Fred” is a terrible name for a component

Kevin Muldoon
UX Collective
Published in
7 min readDec 17, 2022

Image of a “HELLO! MY NAME IS…” tag with the name ‘Fred’ written on it.

Personally, I think ‘Fred’ is a great name. Maybe your name is ‘Fred’. You could be called ‘Fred’, ‘Freddy,’ or even ‘Fredrick’, depending on the familiarity and formality you prefer. It’s very versatile that way.

But if you’re a component in a Design System and your name is “Fred,” I think there is room for improvement.

Dan Mall, one of the biggest influencers, speakers, and advocates of Design Systems, recalls helping Radio Free Europe with its Design System years ago.

When Radio Free Europe was creating a new component, they didn’t know what to call it. Should it be a ‘Carousel,’ ‘Banner,’ or a ‘Slider’? Somehow, they couldn’t reach a consensus, so they bypassed the issue altogether and agreed to call it ‘Fred’.

Right or wrong, ‘Fred’ is used in production at Radio Free Europe as an HTML class today. Dan suggests the longevity of ‘Fred’ is evidence the choice of name was a success.

With that lesson, Dan Mall says, “It doesn’t matter what you agree on. It only matters that you agree.”, and from a certain perspective, this is true.

However, a Swedish Enterprise Architect, Thomas Larsson recalls what his computer science professor once said. “You can call a chair a horse but don’t get disappointed if anyone you don’t know doesn’t understand you.”.

From that perspective, the name is as important as what it does, especially if you want to communicate effectively.

Naming Things is Hard

Naming things is the most challenging aspect of Design Systems, but we need to ask ourselves a difficult question. What makes a good name ‘good’ and a bad name ‘bad’? Is ‘Fred’ a good name or a bad name for a carousel component?

Many articles have been written on ‘how to name components’, but rarely mention when a name is ‘good’ or ‘bad’. Kat Allens' article Naming design system components suggests names that are Intuitive, Consistent, and Scalable as guidelines.

To give credit where credit is due, the component named ‘Fred’ is undoubtedly a triumph in consensus building! However, ‘Fred’ as a…

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Written by Kevin Muldoon

Design Technologist & Product Designer | Helping organizations create with design systems. www.muldoon.design

Write a response

Couldn't agree more! Systems are all built on patterns. If the patterns are incoherent and confusing, the system fails. The great thing about using languages as an example is because language is also a system. Apply confusing patterns to that system and the language itself becomes confusing.

--

I would argue that Fred is a more accurate name for this component as it is more representative of what it actually does – provides a visual display to highlight Featured Content (or f----red for short). This signifies that this content isn't just…

--

Enjoyed reading.
Yes, naming things is hard. And the name we choose can flavor our thoughts when using it or thinking about using it. Call a style class "horrible" and it will probably have to fight for adoption. Call it "pretty" and people will at…

--