There is one very important problem in software engineering: naming accurately.
How many times have you stumbled upon a github repository, a class or a variable wondering what it is used for? Would a more precise and accurate name have eliminated ambiguity in reading a name?
Naming things is as old as humanity itself. It has always been an art to name anything, be it humans, inanimate objects, or abstract idea. The process of naming things varies based on the purpose of naming.
For humans, we name ourselves after positive emotions or the gods, even if we did not possess those qualities that our names indicate. This is fine for naming people, as people are generally complex and a name isn't supposed to really define what or who they are.
Naming, in software, is for an entirely different purpose altogether. The purpose of naming is to indicate clearly what the intended owner (classes, variables, components) of the name is supposed to represent; the complete opposite of what human names are used for. Stereotyping software components has big advantages in the engineering industry as noone wants to maintain software that is as complex as human beings.
Top comments (0)