You Are an Architect. Simplify It.
One of the architect’s responsibilities is not to make things complicated and make it simplify. You can be any type of architects, software, system, technical, solution or enterprise and etc. You should always examine your solution to check if you can simplify. Entropy which is viewed as law of disorder. This is not only second law of thermodynamics in physics. You can see entropy anywhere in your daily life.
The entropy of the universe tends to a maximum
Like the quota above, you can see this law in your IT system, software, hardware, network, database. If it’s not controlled soon or later it will be disaster. How can you know if your solution is complicated? I write couple of questions below to examine your new solution if it’s the right one.
Questions to Examine Your Solution
Ask yourself if it is really necessary? Do not use thing because it’s cool. I remembered that someone bragged about using all knows software design patterns. He did not think if they’re really needed.
Ask yourself what will be the advantageous of having it which could be software, a new logic in your code, additional database and etc.
Ask yourself if you can fix it without adding a new touch point, such as a new server, a new api, a new hardware and etc.
Ask yourself if you can identify a problem in your new solution easily?
Ask yourself if you can fix it easily without impacting other elements such as functionalities, servers, databases and etc.
