Not to mention with an ORM tool you'll have an Employee object, and probably call your collection employees.
Which is better?
foreach (var employee in staff) {
}
or
foreach (var employee in employees) {
}
Which is better?
foreach (var employee in staff) {
}
or
foreach (var employee in employees) {
}
If you're walking on to a new project, these subtleties make all the difference in understanding what's going on without having to rely on documentation.
I basically end up with a "people" table which holds a very small amount of common data and is used in a lot of relationships.
Honestly, the distinctions require a great deal of documentation to fully understand. However, making the data less normalized and a little harder to comprehend also protects new people from making honest mistakes which could lead to legal issues.
Really ? IMHO this is a bad practice : it makes the code les readable and breaks the auto-completion ...
foreach (var e in employees) {
// ...
}