2 ms·
How do you eat an elephant? One bite at a time. Sure, a mass refactoring is going to cause a lot of pain to merge in, but you shouldn't be making massive pull
by marsrover 10y ago
How do you eat an elephant? One bite at a time.
Sure, a mass refactoring is going to cause a lot of pain to merge in, but you shouldn't be making massive pull requests in the first place. I don't think small refactoring here and there should be an issue. It's not like we've never dealt with merge conflicts before.
If your company is discouraging refactoring because it will cause merge conflicts, that's probably not a good sign of things to come.
- marktangotango 10y agoOP didn't mention refactoring, but did mention reformatting? Maybe OP can clarify. In past I've done one big tabs to spaces, trim line ending whitespqce, cr ln to ln, indent cleanup commit. Hardly anyone can object to that! So far as comments I've create multi page wiki documents of the high to medium level architecture. A trail of breadcrumbs in the maze for the next guy/gal. Problem is, those efforts take a lot out of me personally, that stuff sticks in my head years later. Not fun to have the crap i worked on 10 years still on there, I NEED that space :)