> Not less refactoring because we don't care about quality, but less refactoring because we get more right from the start. Requirements always change and infor

> Not less refactoring because we don't care about quality, but less refactoring because we get more right from the start. Requirements always change and information is never perfect. You can't always get everything right from the start because you might not even know what you're trying to get right. If you get malleability right from the start, you'd expect _more_ refactoring, since it's easier to do when you inevitably want to. If you're going to spend effort on trying to get things right from the start, that's where you should focus: Minimize things that are slow change, maximize things that make change less painful. Concretely, this means spend less time code reviewing local variable names and curly brace style; spend more time reviewing public APIs, data format definitions, promised external semantics, etc. with an eye for versioning, deprecating, evolving, etc.