Sounds simple. At some point: isn't. Code gets harder to change as more people and more other code rely on it. Some kinds of usage, and some ways of organizing and managing code, can make the change taxes get nastier faster... or, stay more managable. It's important to understand these and organize code in ways that avoid tax multiplications. Some patterns of action can avoid some change taxes in some situations. It's important to populate your mental toolbelt with these,

I think everyone agrees: we should make this a key part of our culture. "Thinking in the Open" is a huge productivity booster. etc Challenges are: encouraging and enculturalizing this organizing the results (or at least making them discoverable) This is probably subtle: