How beneficial is it to assign code names to big release versions?

There are many software projects that use code names for big releases, like for example Node Argon (4.x) through Iron (20.x).

I have seen this a lot throughout the years, but I am not fully convinced that this is a good practice and I am very curious what people from the wider software development community think of it.

For me personally, it is kind of a double edged sword. Sometimes it is nice for communication with end users, as in "Do you have Android Oreo, or Pie?", since there is a better chance for them to remember the code names instead of the version numbers. On the other hand, I find it a bit unpleasant to work with at times. For example, I don't come into contact with Node much, but when I do, it is usually a build pipeline setup, where I need to pick the right Node Docker image for the pipeline. Requirements often come in version numbers, but Docker images come with code name tags. So I often need to look up the code names again, which is mildly annoying.

​

I assume that there probably are some upsides of having version code names that I am not aware of. What do you folks think about this?