![]() ![]() ![]() ![]() Some possible reasons why migrations can be hard to do: The reality is that many tech migrations (not limited to tech) fail or take much longer than expected. You may ask yourself: “Well, how hard can an upgrade be? Just run npm update or something, and you are good, right?”. Besides, if your framework version is severely outdated, developers will become lazier to try out new things: “ Hey, Angular Universal could improve our performance by a wide margin! Well, too bad, we are still on AngularJS and cannot use it.” Popular third-party libraries or important bug fixes may require up-to-date frameworks. An outdated technology stack makes developers life harder.For example, an outdated tech-stack could prevent you to move as fast as your competitors. Although you should not break things, the idea is that if your tech-stack is stagnant, it might slow you down in your work. It can become more difficult to move fast and break things.Thanks to the open-source community, known security vulnerabilities are often patched in a matter of days. Many security incidents occur due to known vulnerabilities in third-party libraries. An outdated technology stack may turn off candidates. Hiring new talent is essential for any growing company.On the other hand, there are several reasons against standing still: What are the reasons for doing these migrations? You probably know the quote “Never change a running system”. I was part of a small team which wanted to migrate a more than two-year old Angular 4 application with thousands of daily users to the latest Angular version. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |