Reminds me on the place I work. We have many projects for many clients. ASP.NET Web Forms, ASP.NET "old" MVC. We don't have webpack, we use BundleTransformer. We don't have MongoDB, we have SQL Server and NHibernate or Entity Framework. .NET Core is not even on the calendar yet (maybe a little bit sooner now .NET framework is essentially deprecated). We use Knockout, though a replacement is being researched on. Our code is stored in SVN. We use LESS and Typescript 2.x, modern eh?
If you have a single or a small number of products to maintain, because that is your core business, you can afford to upgrade and experiment, revert if necessary. But not if you have many projects, because those projects are per definition smaller. So you take smaller steps, less risky steps. You can't move that fast, it simply cannot be done unless you can create a business case for it.
The real challenge is to resist, as the article states, all the new stuff you get slapped with every day. It is not harmful to say on a bit older technology, technology which may _seem_ to be of another era. It is still useful, and as long as it isn't a business risk it is often not a business case.
If you have a single or a small number of products to maintain, because that is your core business, you can afford to upgrade and experiment, revert if necessary. But not if you have many projects, because those projects are per definition smaller. So you take smaller steps, less risky steps. You can't move that fast, it simply cannot be done unless you can create a business case for it.
The real challenge is to resist, as the article states, all the new stuff you get slapped with every day. It is not harmful to say on a bit older technology, technology which may _seem_ to be of another era. It is still useful, and as long as it isn't a business risk it is often not a business case.