4 ms·
Sometimes you have to upgrade because the old version goes EOL and you won't have support anymore. This is a problem even if you don't add features and it appli
by pmontra 10y ago
Sometimes you have to upgrade because the old version goes EOL and you won't have support anymore. This is a problem even if you don't add features and it applies to open source too.
Example: as soon as Rails 5 gets released, Rails 3.2 won't get any secuurity fix anymore. If the customer accepts the risk of running a system that could be exploited by automated attacks, all fine. If it's not, time to upgrade at least to Rails 4.2. They could also decide to check if the new vulnerabilities apply to their old version and patch it themselves, but it's probably more expensive and error prone.
s/Rails/any other technology/
- vinceguidry 10y agoThat sort of support doesn't just go away. It just stops being free. These guys will happily help you run 2.3 and 3.2 for as long as you want: https://railslts.com/ https://railslts.com/ Again, this usually holds for any reasonably popular stack.
- Drdrdrq 10y agoSure, this happens occasionally, but more often you get an engineer who would like to upgrade just because there is some new version available. Who cares about stability, at least the bugs are new... :( At least that's my experience.
- sanderjd 10y agoMy experience is that more often the engineer knows the good reasons to upgrade but doesn't know how to articulate them to you, especially when you are known to be hostile to the idea of upgrading things.
- Drdrdrq 10y agoActually, I am an engineer, and I myself try to keep up with new technologies. But that doesn't mean I will use them just because they are new - in my mind that is additional risk. I have used my share of technologies which were made obsolete anyway, and it's no fun converting your codebase. But I guess the cool junior engineer who went to another company and left her old company taking care of her project using not-new-anymore / obsolete technology, doesn't care much about that. But I guess if she can't articulate why her newest technology stack is better, we should just switch?</rant>
- mwfunk 10y agoI've experienced both extremes and everything in between, and I don't know that there is any consistent good or bad actor in these situations. Everybody has their own goals and it's human nature to overvalue the things that you care about and undervalue the things that other people care about. Good organizations are set up such that everybody can be a little biased in their priorities but the organization as a whole ends up going down the right path even if no one person is 100% right about what should be done. The decision-making in bad organizations often follows from one type of person with one set of biases making all the decisions. I don't blame people for having biases, I only blame people for denying that they have them and not trying to understand other points of view. However, I can say for sure that there is a widely held view among professionals of all backgrounds (business, technical, whatever) that if someone fundamentally doesn't know how to articulate their point to someone else with a different background or set of priorities, then that person hasn't thought enough about why they should do the thing that they're pushing to do, and that there's a high probability that they're just doing the "overvalue the things you care about/undervalue the things other people care about" cognitive bias that everybody tends to do naturally. I don't know if that's a good rule of thumb or not. There's at least some truth to it. But whenever I'm in a situation where I feel like someone isn't going along with me because I don't know how to articulate my point to them, my first thought is that maybe I need to think about it some more. I don't jump to thinking it's their fault because they don't speak my language.
- sanderjd 10y agoThis is a great comment and I totally agree both that there is almost never an actual "bad actor" and that being able to articulate a persuasive argument is highly valued in decision making. Maybe it is even a decent rule of thumb for coming to decisions under the inevitably imperfect conditions of the real world, but I do think that there are people who are just legitimately poor at articulating things, not because they are wrong or haven't thought things through enough, but simply because they are bad explainers, and that those people tend to be unfortunately undervalued.
- coredog64 10y agoI worked for a CIO who liked to be no more than one major version behind on software. He explained that he had been burned too many times by upgrades that had to go through several versions. If you are going to have to do the work anyways, why not reap the benefits for a while as well.
- StillBored 10y agoYes your right, but not all products (and the product I was initially referring to) have large web facing footprints for security issues. At the indicated company the web facing portion was tiny part of the code base. I did monitor a few key technologies, and back-port or upgrade those (php, apache, ssl, etc) as needed. OTOH, we let our version of gcc get really long at the tooth, as well as refuse to allow additional technology stacks in certain areas (hence no ruby, python, node.js, etc, all rejected because they fill a similar place as the PHP we were already maintaining). Amusingly enough, we avoided heartbleed because our version of openssl was too old! That was fun to try explaining to people, yah we backported the _1_ thing we though might cause a security issue a year ago into our ancient version of openssl, and your not affected by heartbleed. Yes, I know all the version checking scripts say its too old, but try to run one of the legitimate exploits against it.. The second part of this, is that an amusing exercise next time you actually have a need to call "support" for something. Find your local full stack/kernel developer and tell them, hey can you find this critical bug before the support guys find it.. and see what happens. Keeping your toolkits small and lean, with a small set of dependencies does wonders for maintainability.