I don't think game developers are doomed. But the industry is about to change faster than almost anyone expects and I just watched it happen with my own game.

Let me give you a concrete example.

I started building Moonga when I was 17.

After high school, I took a gap year before university and spent the whole year building the first version an online trading card game, back when web games were still in their infancy. It wasn't perfect. It was the work of a young developer. But it worked, people played it, and it proved the concept.

In 2008 I rebuilt it from scratch, created a company, hired a team, modernized rules, redesigned experience, and we spent about a year and a half of work for an iPhone version. We launched on the App Store in 2010. Over the years we invested close to a million dollars. The game became especially successful in Japan and developed a loyal community.

Ironically, our biggest challenge was never creating content it was maintaining the technology.

Back then, iOS and Android meant separate codebases. A web version meant a third. Every feature, every bug fix, every improvement had to be duplicated across platforms. The maintenance cost was enormous.

Fast-forward to today.

I gave Claude Fable 5 the complete source code of Moonga roughly 500 cards, each with its own abilities and gameplay logic. It's years of accumulated game rules, edge cases, and design decisions.

Five or six hours later, I had a fully playable version running on a modern multiplatform stack. One codebase. Web. Mobile. Modern architecture.

A few more prompts and I was polishing interface and gameplay. It's not production-ready I could spend another week on animations, UX, and visual polish. But that's not the point.

The point is this: years of accumulated development knowledge were enough for Fable 5 to recreate the entire game on a modern stack in a single afternoon.

That doesn't erase the original work. Someone still had to invent the mechanics, balance 500 cards, design the systems, create the assets, ship the first implementation. But once that knowledge existed, rebuilding it became almost free.

That's the real shift.

The cost of implementing software is collapsing. The value is moving toward ideas, game design, content, world-building, community, and taste.

We're entering an era where a small team or even a single developer can build what used to take dozens of engineers.

For game developers, that's both terrifying and exciting.

The question is no longer "Can I build this?"

It's "What should I build, now that implementation is no longer the bottleneck?"