is it ever a problem in software engineering, that you can't remember what that component's name is?
I find it more of the problem when people make a good library that solves a problem with a predictable name, but then they give their library some other cute name, and maybe they don't do SEO well on package repositories (why would they, software engineers). So, when I look npm up for that problem, their lib would not even come up.
Yes. When the names are descriptive or bland, it's almost impossible to remember what it is.
This is why I said Boaty McBoatface. You look for Boats? It has "boat" literally two times in it's name.
What I agree with is that it is not strictly necessary, but that is a label that you can stick on a lot of things. Things that make our lives easier. Memorability of names is not a necessity in software engineering, just as is descriptiveness, but it certainly does not hurt.
There are other, less silly, but equally memorable (and maybe even cute) descriptives out there.
On a different note: if you are presented with an either/or choice, your first instinct should always be to ask if they are actually opposites or if you can also have both if clever.