The realism of that mission didn't have much to do with it being successful. It's not a documentary. It was essentially a Star Wars trench run, and they came up with it because it looked super-cool and worked for the plot. They did an excellent job of pacing that movie and building tension. We're told over and over again that the chances of success are slim. The second time I watched it, even though I knew what was going to happen, as they were approaching the coast I was still on the edge of my seat. That's hard to do.
No, that movie was about a bunch of relatable aspects of life. Pete's growing older. It realistically portrays the feelings a person has about passing the torch to the next generation. You have a lot of experience and you want to protect them from their own mistakes, but you know that you're not doing them any favors by holding the umbrella over their head. There's the regret over what could have been with Penny. There's the regret over what he did pulling Rooster's papers, even though it was Rooster's mom who made Pete promise to do it. And the competing responsibilities. These are all feelings that older people really have.
The first movie was aimed at teenagers, and it hit the bullseye. Those people are getting older now, and have a different perspective on life. I give the writers credit for creating a legacy sequel that follows up on a story with the same audience as the original, and keeping it relevant to them. They hit the bullseye again. If Disney had made this movie they'd want to rejuvenate the brand and make it cool for a new generation, and it wouldn't have worked as well as it did.
I maintain and develop on a large LOB application with many hundreds of thousands of lines of code. I find AI to be useless when trying to write a new function or class because it doesn't understand the architecture and structure of the codebase. Or maybe the context size just isn't anywhere near big enough. It also doesn't understand the specific aspects of the business that are important. We don't write our own accounting system because you can just buy one. But if you want to automate some process that's unique to the success of your company, there isn't going to be much out there in the training data for the LLM to draw from.
However, there are a lot of developers who spend most of their time writing greenfield code. Someone gives them an assignment or a contract that's very spelled out... "install a shopping cart on my such-and-such website". This is more like integration work and actual development. It's the same implementation repeated over and over for site after site. I can appreciate that this is an area where an LLM can probably provide a lot of value.
But not all developer work is so cookie-cutter.
Worldwide we have an aging population and that means by definition that we're going to retire far more people over the next 10 years than we graduate from school. The workforce as a percentage of the population will decrease. The graduates of the next decade have already been born.
The point is that it'll force more of our resources towards paying for people who aren't participating in the workforce. Either we'll stop taking care of our elderly parents (not likely) or every other part of our society is going to be forced to take a budget cut. This isn't all just about luddites who don't want to fund research. This is about shrinking resources. We knew this was coming decades ago. It's not news. It's not surprising (except to the people who weren't listening). Most importantly there's absolutely nothing we can do about it. Demographics is one of the most predictive disciplines.
There will be less resources spent on research, whether we like it or not.
If all else fails, lower your standards.