Ask HN: Naming Things
It's upfront design, because you name before you use. You can use "working titles", and syntax-aware IDEs help renaming, though it becomes harder to navigate/search in version control, when files, directories and functions/classes are renamed.
I think you should name interfaces in terms that make sense from the user perspective, not from the implementor perspective.
There was discussion in https://news.ycombinator.com/item?id=20259850
I'd like to name well, but it's difficult, and I'm seeking a justification to invest in it. But if code changes often or is short-lived, is it worth the investment? It's technically satisfying to do, but is polishing something transient worth it? As I code, my idea of the design often changes, which means different names are appropriate... OTOH if complexity is becoming a show-stopper, then it's essential.
Thoughts?