Do column ID's use acronyms?

Do column ID's use acronyms?

• A. No
• B. Yes
• C. Sometimes
• D. Always

Answer: (A)

Column identifiers should be descriptive and self-explanatory. Acronyms tend to obscure meaning and can vary by team or project, which hurts readability. When naming a column, aim for clear terms like customer_id, order_date, or total_amount_usd. This makes the data’s purpose obvious at a glance and reduces the need to consult documentation. A data dictionary can document any acronyms you do use, but the column name itself should stay readable. Therefore, column IDs do not inherently use acronyms; the default is to avoid them to keep data understandable.

Column identifiers should be descriptive and self-explanatory. Acronyms tend to obscure meaning and can vary by team or project, which hurts readability. When naming a column, aim for clear terms like customer_id, order_date, or total_amount_usd. This makes the data’s purpose obvious at a glance and reduces the need to consult documentation. A data dictionary can document any acronyms you do use, but the column name itself should stay readable. Therefore, column IDs do not inherently use acronyms; the default is to avoid them to keep data understandable.