naming things

A good name makes the next line of code easier to write. A bad name makes every future reader slightly more confused than they need to be, forever.

data, info, manager, handler, util — these are names that gave up. They defer the question instead of answering it.

Name things by what they do, not by what they are. UserEmailSender over EmailService. fetchActiveOrders over getOrders. The specificity is the point.

If you can’t name something clearly, you probably don’t understand it clearly yet. The naming problem is often a thinking problem.