DDC, code and architecture (continued)
What I was going to say in my previous post was that in software systems, there are organizing principles specific (more or less) to the sets of problems addressed by them. If these systems are well designed, every potential addition should have its obvious place.
By this I do not mean that every potential addition should be anticipated, but that the design should be evolved in a way such that it’s perfect at every stage, liquid, changeable.
When I thought about this, I found it interesting to consider the differences between the organizing principles of individual systems and those of a “reuse library”.
But I lost that train of thought.