Typos are find-and-fix-once, while unsearchability is a maintenance burden forever. I don't think coupling variable names by making sure they contain the same

Typos are find-and-fix-once, while unsearchability is a maintenance burden forever. I don't think coupling variable names by making sure they contain the same strings is the best way to show they're related, compared to an actual map from address type to table name. There might be a lot of things called 'shipping' in my app, only some of which are coupled to `shipping_addresses`. Shouldn't a linter be able to catch that there is no enum member called MyEnum.ATRISTS, or is it not an actual enum?