When to upgrade your software and when not?! (عربي)

#softwareupgrade
Taking a decision to upgrade an application/ product/ code is not always a simple one. Difficulty sometimes goes to factors like:
1. Size of an application or a product.
2. Lack of expertise.
3. Return On Investment (ROI).
Size of the application
Size here could have two meanings:
How big the application is in terms of the architecture and the components and inner systems that the application or the product is made of. Applications that are tightly coupled to specific technologies are subject to be irreplaceable or difficult to upgrade. Here comes the role of the abstraction and the necessity to decouple the communication between the internal application units and the underline technology that serves it.
How old the application is in the market and how many customers or other applications rely on it. When the application or the product has a delivery plan to its customers. It would be tough for teams or even the top management to support the upgrade decisions. They would prefer to stick to the plan they have to deliver the features they promised their customers to have when their applications would be released. For teams who work on the development of the application, they sometimes defer taking actions on some weak decisions they take due to tight delivery plan and this results to technical debt that sometimes gets lost and thus could lead an application or the project as a whole to fail!
لقراءه المقال كاملا
codewithtolba....