3 ms·
I don't say you should never use "customers" over "list", but the latter is often good enough. List is a good fit for a compact method which is doing something
by Yokohiii 8y ago
I don't say you should never use "customers" over "list", but the latter is often good enough. List is a good fit for a compact method which is doing something generic on a list or the context clearly specifies what is in it. It is of course a matter of what you are doing. The point is, that being very specific every time is likely overkill.
- jdmichal 8y agoYou keep saying if it's obvious in context, but context is a name for "one more damn thing I have to keep track of." Which is why I call it inconsiderate; you are forcing other developers to constantly have to build and maintain their mental context of what is going on. "Oh, great... Here's another `list` variable, let me go see what it is this time."
- s73v3r_ 8y agoI disagree. There's practically zero cost to writing "customers" instead of "list". The only time it really makes sense for it to be "list" is when you're writing generic methods that just know it's a list.