One important fact to acknowledge is that even if a software system consists of a lot of code - there is difference in the purpose of different types of code.
We at MDriven has made it our mission to clarify the 3 different areas that create reasons for having code. We call the 3 areas Fashion, Gist and Modernity.
The code needed for the infrastructure of the system to work - databases - network-transport - programming language - physical tiering etc. - all this we classify as Modernity-code. We gave it the name Modernity because this type of code is very time dependent. A system created ten years ago looks different in its modernity-code just because the progress of software infrastructure architecture has changed. Many systems has changed from one language to another, changed from fat-client to web, changed from on-premise to in-cloud etc.
All the code that has primary purpose to create a finish and the right look and feel goes into the Fashion classification. Fashion - like Modernity - does not age well. Both Fashion and Modernity is under heavy change pressure from the progress of technology - and fashion trends. Five years ago no one talked about MaterialDesign - but now its everywhere - for how long?
The third kind of code is what describes "the Gist" of the system - namely what information is the system handling - and what business rules guard the dynamics of that information. This kind of code has a totally different life cycle compared to Modernity and Fashion. The Gist change is driven by the progress of internal and external business processes rather than a non business specific environment.
Since only idiots hard-fix things with different lifecycles together it seems as something we to must avoid. You have screws on your light bulbs in your house - because light bulbs break more often than the house itself. You change curtains and wall-paper because you get tired on the old ones - it is easier than tearing down the house and re-build.
It is obvious for smart people that we need to be able to change the Fashion independently of the Modernity and let the Gist live on - in its own lifecycle.
With MDriven's Vision we want to deliver on these insights.
We believe that following these posits will earn businesses a lot of money. Both in faster time to market - and having a system with a better fit to said market - over time. But the not so obvious benefit is the ability to hold the Gist of the system in a high level description that not only act as the motor of the software but also act as the best available structured understanding of all the information that the business currently handle. And when this kind of artifact is present in a community of people that community gets a common language that enables a high level and high precision business discussion on what to do next. And this is priceless for forward thinkers.
You can read on our Vision here https://blog.mdriven.net/the-mdriven-vision-explained/