2 ms·
I don't understand your point. You would like to know which techniques that minimize work involved in maintaining a codebase / adding features ? It's true that
by ttoinou 9y ago
I don't understand your point. You would like to know which techniques that minimize work involved in maintaining a codebase / adding features ?
It's true that it's a topic not very well researched but you also have to take into account others factors (economic, management, incentives, planning etc.). For example, following Conway's law ( https://en.wikipedia.org/wiki/Conway%27s_law https://en.wikipedia.org/wiki/Conway%27s_law ) the software codebase complexity and the way the team is organized are connected. There might be no silver bullet at all (e.g. it's a hard problem involving human coordination)
- scotch_bright 9y agoOkay. I will study more about Conway's law. Thanks for that. What I want to get at is: Is this the "normal" state of affairs? Do all projects devolve eventually? There seems to be a lot of work that has been done on Deign Patterns and best practices to write code etc etc. And this work was done 20-30 years ago. So, what explains the mess we see everywhere? Thats what I want to find out.