As you stated yourself, problem is not that common in Frontend because of Feature Modules approach and narower scope, but if you ever open complex backend codebase that deals with CQRS and other patterns or implement Custom Framework than big problems arise with and from naming.
Custom Frameworks tend to use generics and interfaces a lot and rather sooner than later Keywords such as Implementation, Mapper, Reader, Action, Model, Factory, Subscriber, ServiceChannel, Set, Result... (name it based on domain and technical usage) will become useless and not clear.
How to avoid it, define your domain (DDD) early on and stick with it. PERIOD.
Make everyone use agreed upon names and even if your names are long they will make sense and will be uniformed.
Discouss names for new classes with your team regularly and pick best options :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
As you stated yourself, problem is not that common in Frontend because of Feature Modules approach and narower scope, but if you ever open complex backend codebase that deals with CQRS and other patterns or implement Custom Framework than big problems arise with and from naming.
Custom Frameworks tend to use generics and interfaces a lot and rather sooner than later Keywords such as Implementation, Mapper, Reader, Action, Model, Factory, Subscriber, ServiceChannel, Set, Result... (name it based on domain and technical usage) will become useless and not clear.
How to avoid it, define your domain (DDD) early on and stick with it. PERIOD.
Make everyone use agreed upon names and even if your names are long they will make sense and will be uniformed.
Discouss names for new classes with your team regularly and pick best options :)