On coding: refactoring only after usage proof

I rewrote a module because it "felt messy." Zero user impact, two weeks gone. The new code was cleaner; nobody noticed. Now refactors need a trigger: performance data, bug cluster, or feature blocked by structure. Cosmetic refactors wait until Friday afternoon or never. Code quality is a means—faster shipping, fewer incidents—not a hobby separate from customers.