This is such a simple idea. People often want to break up the three things, though.
#objectoriented @IndustrialLogic
#objectoriented @IndustrialLogic
The name is key here. What is this object for? Why would anyone look for it, or use it? When I'm programming, and I need a skiplist where can I find it, and what is it called there? What if it's not called skiplist?
Sometimes this is simple, like python 'datetime' contains 'date', 'time' 'datetime', 'timedelta', and more.
The name 'date' is scoped, so the name is really 'datetime.date' which is important to realize.
The name 'date' is scoped, so the name is really 'datetime.date' which is important to realize.
The scope should add meaning and context to the immediate name.
It may be that 'partial' wouldn't mean as much to a developer as 'functools.partial'.
Likewise 'Counter' in 'collections' probably is more appropriately meaningful than it might have been in 'itertools'.
It may be that 'partial' wouldn't mean as much to a developer as 'functools.partial'.
Likewise 'Counter' in 'collections' probably is more appropriately meaningful than it might have been in 'itertools'.
But in each case, the (fully scoped) name is supposed to make it easy to find the functionality you are after.
It should evoke an idea of what it's for, rather than what it's made of. The fully-scoped name should be sensible.
OO is a kind of filing system in that regard.
It should evoke an idea of what it's for, rather than what it's made of. The fully-scoped name should be sensible.
OO is a kind of filing system in that regard.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
