Naming for the future

How we ended up here: There is never enough time.

Software evolves over time. Example: When writing the software, a developer creates a simple object and calls it Provider. Later, there’s a need for another object quite similar to Provider, so the harried developer takes most (but not all) of the attributes of the object Provider and creates a class (which contains the original object). Which class the developer also calls Provider. There’s no time to think of another name, and even if there were all the time in the world, the developer might not see a need to apply a better name.

[Read More]