Is it best practice to create a mapping table for translating technical column names to user-friendly descriptions in PHP?

It is a best practice to create a mapping table for translating technical column names to user-friendly descriptions in PHP as it improves the readability and usability of the code for end users. By using a mapping table, developers can easily maintain and update the descriptions without changing the actual column names in the database.

// Mapping table for translating technical column names to user-friendly descriptions
$columnMapping = [
    'id' => 'User ID',
    'username' => 'Username',
    'email' => 'Email Address',
    'created_at' => 'Registration Date'
];

// Example usage of the mapping table
$columnName = 'username';
if(isset($columnMapping[$columnName])){
    $userFriendlyName = $columnMapping[$columnName];
    echo "User-friendly name for column '$columnName' is '$userFriendlyName'";
} else {
    echo "User-friendly name not found for column '$columnName'";
}