No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
One important fact to acknowledge is that | One important fact to acknowledge is that although software systems consist of a lot of code, each type of code has a different purpose. | ||
At MDriven, we have made it our mission to clarify the 3 different areas that create reasons why code exists. We call the 3 areas: '''Fashion''', '''Gist''', and '''Modernity'''. | |||
==== Modernity ==== | ==== Modernity ==== | ||
This is the code the infrastructure of a system needs to work. Databases, network-transport, programming language, physical tiering, etc. - all this we classify as Modernity-code. We named it Modernity because this type of code is very time-dependent. A system created ten years ago looks different in its modernity-code because the progress of software infrastructure architecture has changed. Many systems have changed from one language to another, from fat-client to web, and from on-premise to in-cloud, etc. | |||
==== Fashion ==== | ==== Fashion ==== | ||
All the code that has primary purpose to create a finish | All the code that has the primary purpose to create a finish, the right look, and feel is in the Fashion classification. Fashion, like Modernity, does not age well. Both Fashion and Modernity are under heavy change/pressure from the progress of technology - and fashion trends. Five years ago, no one talked about [https://material.io/design MaterialDesign] - but now it is everywhere, however, for how long? | ||
==== Gist ==== | ==== Gist ==== | ||
The third kind of code is what describes "the Gist" of the system - namely what information | The third kind of code is what describes "the Gist" of the system - namely what kind of information the system is handling and which business rules guard the dynamics of that information. This type of code has a completely 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 nonbusiness-specific environment. | ||
==== Our | ==== Our Posits ==== | ||
Since only | Since only fools hard-fix things with different lifecycles together, it is something we must avoid. You have screws on your light bulbs in your house because light bulbs break more often than the house itself. You change the curtains and wallpaper when you are tired of the old ones; it is easier to change those than tearing down the house and rebuilding. | ||
It is obvious | It is obvious to smart people that we need to change Fashion independently of Modernity and let Gist live on - in its own lifecycle. | ||
==== Vision ==== | ==== Vision ==== | ||
At MDriven, we want to deliver these insights with our vision. | |||
We believe that following these posits will earn businesses a lot of money | We believe that following these posits will earn businesses a lot of money, both with faster time to market and having a system with a better fit to said market - over time. The not-so-obvious benefit is the ability to hold the Gist of the system in a high-level description that not only acts as the motor of the software but also acts as the best available structured understanding of all the information that the business currently handles. 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. This is priceless for forward thinkers. | ||
==== Video ==== | ==== Video ==== | ||
Revision as of 09:58, 16 January 2023
One important fact to acknowledge is that although software systems consist of a lot of code, each type of code has a different purpose.
At MDriven, we have made it our mission to clarify the 3 different areas that create reasons why code exists. We call the 3 areas: Fashion, Gist, and Modernity.
Modernity
This is the code the infrastructure of a system needs to work. Databases, network-transport, programming language, physical tiering, etc. - all this we classify as Modernity-code. We named it Modernity because this type of code is very time-dependent. A system created ten years ago looks different in its modernity-code because the progress of software infrastructure architecture has changed. Many systems have changed from one language to another, from fat-client to web, and from on-premise to in-cloud, etc.
Fashion
All the code that has the primary purpose to create a finish, the right look, and feel is in the Fashion classification. Fashion, like Modernity, does not age well. Both Fashion and Modernity are under heavy change/pressure from the progress of technology - and fashion trends. Five years ago, no one talked about MaterialDesign - but now it is everywhere, however, for how long?
Gist
The third kind of code is what describes "the Gist" of the system - namely what kind of information the system is handling and which business rules guard the dynamics of that information. This type of code has a completely 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 nonbusiness-specific environment.
Our Posits
Since only fools hard-fix things with different lifecycles together, it is something we must avoid. You have screws on your light bulbs in your house because light bulbs break more often than the house itself. You change the curtains and wallpaper when you are tired of the old ones; it is easier to change those than tearing down the house and rebuilding.
It is obvious to smart people that we need to change Fashion independently of Modernity and let Gist live on - in its own lifecycle.
Vision
At MDriven, we want to deliver these insights with our vision.
We believe that following these posits will earn businesses a lot of money, both with faster time to market and having a system with a better fit to said market - over time. The not-so-obvious benefit is the ability to hold the Gist of the system in a high-level description that not only acts as the motor of the software but also acts as the best available structured understanding of all the information that the business currently handles. 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. This is priceless for forward thinkers.
Video
You can read on our Vision here https://blog.mdriven.net/the-mdriven-vision-explained/