When I say long name I wasn’t implying meaningless ones.
Sooo, that example wasn’t exactly “contrived” - it’s based on a standard I see where I work.
DB - it's a database!
DW - and a data warehouse at that!
ORCL - It's an Oracle database!
HHI - Application or team using / managing this database
P - Production (T forTest - love the 1char difference between names!)
01 - There may be more than one.
This is more what I’m arguing against - embedding meta-data about the thing into its name. Especially when all of that information is available in AWS metadata.
[Site][service][Rack] makes sense for on-premise stuff - no argument there.
I’m just saying long names dont have to be obtuse or confusing.
Sooo, that example wasn’t exactly “contrived” - it’s based on a standard I see where I work.
DB - it's a database! DW - and a data warehouse at that! ORCL - It's an Oracle database! HHI - Application or team using / managing this database P - Production (T for Test - love the 1 char difference between names!) 01 - There may be more than one.This is more what I’m arguing against - embedding meta-data about the thing into its name. Especially when all of that information is available in AWS metadata.
[Site][service][Rack]makes sense for on-premise stuff - no argument there.Agree