Name things twice and you named them wrong

One concept gets one name. When the same thing answers to two names, the code is telling you something is off.

Aliases are debt

Adding a second name is the cheap fix. It works today and costs every reader after you, because each one has to learn that the two names mean the same thing.

Rename at the source

If a name is wrong, change it where it is defined and follow it through the callers. A wrapper that translates the old name into the new one leaves both alive.

Duplicates point at a gap

Two names often mean two half-abstractions doing one job. Merge them, and the naming problem disappears with the duplication.

When two names are right

Different layers may honestly see different things. A record in the database and a value in the UI can differ in shape and scope, so they can differ in name.