Menu
I'm currently working on a site which went through god knows how many developers' hands. One of the things I don't like about it is the way every table in the database has the prefix "tbl_" and every field "fld_".
I've started work on a new feature and I'm faced with the following problem: should my new tables continue with the old convention, or not?
I guess I should, but I feel stupid doing it :)
545
Naming conventions make sure users know how to name digital assets so that filenames or titles are consistent and contain all the right information. They help you store and organise your files. Without them, your asset library can become chaotic and make it much harder to find images when you need them.
Using descriptive, consistent naming conventions is important and should not go overlooked. Variability and inconsistencies often lead to confusion, error and loss of time.
If there are different naming styles in the project, it keeps to distribute the engineer concentration. From time to time, engineer doesn't want to work on a project which is hard to understand the code.
Difficulty of Enforcement – even if an organisation chooses to implement conventions for Team names, how can the organisation ensure that users follow these rules. Poor perception – enforcing rules like naming conventions can result in users viewing Teams as another tool where IT put barriers in place.
I would keep the same convention.. Regardless of if it's bad or not at least it would be consistent. And consistency will be very important to the next developer who gets ahold of the code.
87
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
