Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Naming is hard. It requires an understanding of what a thing does (or more accurately, at the time of coming up with the name: what the thing WILL do).

One useful practice I've acquired over the years is to make the names unique. It makes it easier to search for them later.

Generally, I would lean towards descriptive names. If the name no longer fits the thing, that's a great warning about scope issues. If it sounds "weird" for other named things to be dependent on or be required by the named thing -- that's often a hint about a context issue.



Naming is hard.

I mean, there's a reason the old joke goes:

"There are only two hard problems in computer science; naming things, cache invalidation, and off-by-one errors."




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: