Once a particular domain of software becomes sufficiently mature, there is no real opportunity for heroic programmers to emerge who become too valuable to replace. Eventually more people emerge who are just as good.
I... have you played games at all recently? Have you seen the recent major releases? BF2042, Cyberpunk, etc. Even the highest quality game studios (not the aforementioned) have trouble making good high quality releases, especially with consistency.
Games are certainly not a solved problem.
we see the same attitude in software industry - somethin' that has existed since the 60s that software is solved problem. yet everyone has difficulties in shippin' software that actually works whether that's titans like Apple / Microsoft to small mom and pop shops.
Games the difficulty is two-fold. 1: games are an art - and making art to good taste is a complex problem. 2. games are software - thereby suffering from problems encountered by the regular software industry etc lack of labour / resourcing etc
But games are not a solved problem. There are multiple overlapping reasons why.
One is that gamedevs often just don't do the research. Why would they? The deadlines loom, the milestones have to be delivered, nobody cares if it's a hacky mess right now, surely management will give us time to fix it once they realize that it's broken--but if we don't deliver anything, the publisher cuts our funding.
This overlaps with scheduling and management issues. It turns out that writing good software takes up time[1], and the problem with games in particular is that they don't make money until they're released.
You don't write games like you write business software, where the other company paying for your milestones is the company that's going to use the software; that company usually has a revenue stream even without your software, so they don't have to care as much. For a game, though, there IS no revenue stream until the game launches. Every year that a game is in development without a release is a loss, and that pisses the board of directors right the fuck off, so that means the game needs to be out ASAP.
Because of this, games are often not given enough room in the development schedule to be made correctly. There's no time for research, testing, planning, or any of the other important parts of software engineering--we have to write this code NOW, or it doesn't ship. And if you read that source I linked in the footnote, you'll know that this produces rotten software.
This is compounded by the kind of one-upsmanship that is created by such an environment--leading to a phrase I've heard from friends in other companies: "Very optimistic people who are no longer with the company made this decision". You get into a situation where people made promises to impress the publisher, claiming that they can turn out a game in an impossible timeframe, and that got them fired--but now you're stuck cleaning up the mess, and the publisher has already wasted a lot of money on the years spent thinking it wasn't a mess.
Mix in the siloing of information (because all of this shit is proprietary) and, despite all of the problems being solved on paper, nobody's solved video games.
I could be out of loop, but the last time I played Dwarf Fortress, it still used terminal graphics and white I believe in gameplay > graphics, my brother and the majority don't and probably won't even touch the game. (Not to mention the _menues_)
That is why we have so many bland but technically impressive games. Studios want safe bets, an FPS game is easy, making it interesting to play is still very hard.
Game engines and graphics is "solved" if you stick to popular concepts (which are those that are easily available in commercial engines).
Game design/mechanics is an unsolved problem imho - unless you consider it solved when merely taking an existing game design (like an FPS) and add nothing new to it (aka, those yearly COD military shooters).
Consider a game like https://store.steampowered.com/app/1141580/Taiji/ (inspired by the witness). This game is quite unique, and cannot really be recycled in to another game (without it being just a clone).
As they say: All good things must come to an end.
And: You either die a hero or live long enough to become a villain.
Many game devs are fungible cogs, implementing a well-defined blueprint. Especially Activision games like Call of Duty. It doesn’t help that there’s just so many devs these days that they can seemingly abuse them for decades and nothing has collapsed.
Even simple boilerplate is done differently by people. Some will automate them, some will do them manually forever. Some will naturally organize to discuss how to limit or improve them, some will stay with the status quo ad vitam. Some will document how to do things, provide templates to limit mistakes and mentor new comers. Some will just do their job.
And that's not even touching the fact some are simply bad at what they do.
In all the successful projects I've seen, hiring the right people or replacing the one leaving were critical processes, not just swapping.
This idea you foster is probably half the reason 2/3 of IT projects fail.
It's also an area where there's more and more outsourcing happening these days.
I mean, I'm sure they wouldn't implode, but I bet they pay their core engine devs a more than decent wage.
I once left a company quickly after a senior leader had left. That proved to be a good move since the company was going under and sold a few months after.
Some of them probably get 50 applicants for every position they advertise. It's a meat grinder.
Video game developers don't have terrible conditions and relatively low pay because of some anomalous lack of bargaining power which can be fixed by unionization. They have lots of bargaining power, most of which they use to choose the industry they work in. There are lots of young men who want to work in games, and far fewer who want to work in financial software. So pay and conditions are far worse in games, to the point where supply meets demand in each type of development work.