Never update anything | blog.kronis.dev
My blog, where i attempt to collect my thoughts and share the occasional interesting topic with others
This article takes the argument to the extreme and one interpretation of this is that it’s a great rant. However there’s a lot of useful nuggets of information here around how software development has evolved over time. Goes deep into dependency management, patching, and development and deployment models.
“When you're telling your colleagues that you can't really work because Windows or JetBrains IDEs need to install some updates, they'll give you understanding, yet annoyed glances. When you tell clients that you cannot ship software because first you need to spend a few days or weeks refactoring software to keep up with the latest library releases, they will express their displeasure at you and will probably look elsewhere for someone who won't care about updates. When your company won't be the first to market, because about 20% of your total development capacity needs to spent on keeping up with the technical debt, which is slowly forced upon by the industry, while another 20% of the effort needs to go to writing and maintaining a test suite, the company will suffer as a result. And once you actually do get the buy-in to update the components and when it turns out that migrating from Spring to Spring Boot is actually a herculean effort that means carrying over about 50 dependencies of a legacy Java project that has about 1 million SLoC, during which you also discover that at least 20-30 of those are painfully out of date, then you'll just start writing blog posts like this”Posted on 2021-11-06T06:34:47+0000