News for hackers. Stuff that matters.
Re:How to name things: the hardest problem in programming (2... by bulatb on Tuesday June 20, 2017 @05:33PM (#14598821)
Naming things is hard because a proper name imparts the essence of the thing you're naming. To understand the essence of the thing, you have to understand what role it serves, what else it interacts with, and what part of that is interface and what is implementation.

Naming is identifying concepts that matter—and occasionally realizing that the thing you just wrote, but can't name, is not a thing that should exist. It's part of understanding what your system really is and what it does.

The naming part, the mapping of words to objects, is easy. What's hard is breaking down a system into parts with obvious names.

Re:How to name things: the hardest problem in programming (2... by InclinedPlane on Tuesday June 20, 2017 @07:50PM (#14599523)
Indeed, naming things is hard because it involves design, and most often design is just a mess (a big ball of mud). Which is good, because bad names are a code smell. If you find yourself with lots of manager, doer, handler names maybe you should revisit your architecture. If you find yourself with lots of stuff that is similarly named or all shares the same naming prefix, maybe spin that chunk off into an object or something.
Re:How to name things: the hardest problem in programming (2... by assadk on Tuesday June 20, 2017 @06:53PM (#14599256)
Well said.