On Nomenclature in Code
TechnicalName entities - whether variables, classes, tables, fields, methods or anything else - according to what they are...not according to how they're being used. Seriously. I've lost hours of my life searching big-gulp-sized data models for the email_address field only to find out that a user's email address is being stored in username. Hours I'll never get back.
alynch said:
If you could only get a load of the databases we have to deal with here at work.
OMG terrible. There have been many hours spent searching/guessing/etc to find out what some cryptic fieldname really meant.
OMG terrible. There have been many hours spent searching/guessing/etc to find out what some cryptic fieldname really meant.
.: HIDE REPLIES :.
rwilkerson said:
That's a worse sin, I think, but it's usually easier to get people to provide human-readable names. I've found it harder, in some cases, to get people to divorce the data itself from its application within the...well...application.
That said...I'm glad I don't work where you work. :-)
That said...I'm glad I don't work where you work. :-)
Loading....