The reason Leo 1.5+ million lines of code work reliably is that Leo's
design ensures that almost all code has strictly local effect. Leo's
developers can add new features without fear of breaking other code. Furthermore, Leo's overall design has remained remarkably stable for over 20 years.
I learned the practical techniques from two giants. This was in the 1970, way before classes were invented:
David L Parnas wrote
On the Criteria to be use in Decomposing Systems into Modules.
Glenford Myers wrote
Composite/Structured Design.
Both are well worth reading today. In essence, they talk about the properties of "strong" classes.
The next post shows how this works in practice.
Edward