Be careful before you write off existing software as bad design, you are probably making the same choices yourself!
When you’re an architect, you inevitably find yourself the proud owner of a system or product that you didn’t design but that’s been serving its users for years. This can be a traumatic experience, particularly when you find yourself staring at the results of decisions made under death march pressure, or built with technologies that passed their prime 10 years ago. In those cases its difficult to believe but there is no bad design, only better design.
All developers and architects do their best to make technical decisions based on the following inputs:
If you assume that the developers and architects that came before you tried just as hard as you would to find that perfect middle ground between the three laws of software, then why does the software look so poorly built? The answer is time; time has an affect on all aspects of software design.
When any of these constraints change because of time, another, “better” decision becomes clear. When you’re looking backward at those decisions the constraints inevitably have changed. All you can do is make a better design and hope that the architect who gets your work some time in the future understands the constraints that led to your decisions.
Microsoft Azure and Amazon Web Services (AWS) are two of the most popular cloud platforms.…
Cloud management is difficult to do manually, especially if you work with multiple cloud…
Azure’s scalable infrastructure is often cited as one of the primary reasons why it's the…
https://www.youtube.com/watch?v=wDzCN0d8SeA Watch our "Unlocking the Power of AI in your Software Development Life Cycle (SDLC)"…
FinOps is a strategic approach to managing cloud costs. It combines financial management best practices…
Using Kubernetes with Azure combines the power of Kubernetes container orchestration and the cloud capabilities…