3 ms·
> If you're going to refactor, don't refactor in the direction of new. Refactor in the direction of coherency. 1000x times this. And making things coherent wil
by jrochkind1 12y ago
> If you're going to refactor, don't refactor in the direction of new. Refactor in the direction of coherency.
1000x times this. And making things coherent will make it a lot easier to put the new hotness in too. Add in the new hotness only when you can do it in a coherent way. If you can't do it in a coherent way, you might need to refactor until you can get there.
You might never get there in a legacy codebase, but if everyone took this attitude from the start, you might be less likely to end up there.
You can put new things in and change architecture, but you always have to do so coherently -- which does mean you can put in fewer new things, and sometimes not the new things you want to put in as soon as you want to put them in.
And oh, yes, so very much: "don't treat organizational problems as technical ones." Without understanding the organizational disfunction at the root of your technical issues (it's almost always there), you're doomed. Of course, then you've got to figure out what to do about the organizational problems (or how to operate succesfully in their shadow), which is not what you find the most fun part of your job, but that's how it is.