April 13, 2026 at 12:00 am
Comments posted to this topic are about the item Poor Names
April 13, 2026 at 12:31 pm
As a data architect, I'm always preaching about using consistent standards to enforce names, data types, etc. The value of a standard isn't in the method of naming or data types used, but it's consistent application and use across the board. That means that if a change to the standard is absolutely requried, so is the application of that standard everywhere even if it means going back and changing things already in production.
Of course, throughout my career I have developed personal preferences for such things, but those are subservient to consistent application. For example, I should be able to open a stored proc and not know who wrote it because it follows the standards established in formatting, naming, data types, and application. It reduces time to implement changes, reduces the possibility of errors that inevitably increase time to resolution, and improves data quality.
Consistency is King! Long live the King!
LinkedIn: https://www.linkedin.com/in/sqlrv
Website: https://www.sqlrv.com
April 13, 2026 at 3:50 pm
Agreed, Aaron. I've often caught this stuff in code reviews since so many humans are poor stewards of consistency, including their own.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply