> If you never have to come back to “fix it”, was it actually wrong to begin with? 1. Ah, we often "have to", but also aren't allowed to because it would rock

> If you never have to come back to “fix it”, was it actually wrong to begin with? 1. Ah, we often "have to", but also aren't allowed to because it would rock the boat too much and take too much time. 2. Unfortunately, too many coders share your attitude, and then other people have to work with what you guys left us - facing the consequences of making it do something which is different than the original settings, and being stuck with some jerry-rigged and inflexible set of assumptions. At least sketch out in comments what the better solution was supposed to be and where you cut the corners!