Plural conventions

Memorability is a key component of software development. So please, when you are developing software, pick a plural convention and stick with it. If you are going to call your database table “users” (since it holds many user records), then refer to your model with the same plural. If your user object is an instance of one user, then please refer to it singularly as “user”. The same rules need to apply throughout your design and implementation.

The key is that it should be easy to remember the convention once you know the rules (and the less rules, the easier it is to remember them!). I don’t mind what rules you use. The problem, and reason behind so many developer flame wars, is inconsistency. We think in patterns and systems, and nothing irks us more than when those patterns and systems break for no good reason.