While I was there a colleague of mine taught me to only ever talk in singular form, the reason being that at the end of the day one piece of data will always be in its own right unique.
When I program, I have a tendency to stick to the rule he taught me, and I have to admit it definitely makes perfect logical sense. What I personally hate is people pluralizing the name of a function or variable.
So here's the main goal:
- It's not the "users" table, it's the "user" table, why?
- The row data will always equal one user, so call the table "user". It is the user structure.
- When you want to relate to the table, "users_id" won't make sense unless you meant "user's_id" or "id_of_user", it should be "user_id"
- Why call it the users object? It's the user object.
- It's not the "getUsers()" function, it's the "getUserList()" function. Why?
- It's not the Users object, it's the User object, you want a list of them.
- A list is a singular form of data containing more singular forms of data.
- Pluralizing the name of the forms of data restricts the amount of variability of the word list. It's the form of data that is variable, not a list.
- It's not $users, it's $userList. Why?
- The object is not called Users, it's the User object, and you are storing more than one of them.
- It's not the $buckets, it's the $bucketList.