human readability of database during reviews

[TeoTwawki]

#3673 (comment)

snip

I'd rather we just have a a name field and shift all of them into it (saying the rate after is redundant, esp after I made the @variables).

DSP shot down such suggestions back in the day saying "you can use a join query" as if we're going to review by running queries locally. They ain't here - just need 2 devs to approve. I'm one.

end snip

Like half our name fields exist solely for human readability - whats a few more?

Or should we hold off for tooling to make it not matter?