# A pragmatic view on the use of AI in game development — retained record

> Retained reddit record from reddit:gamedev.

Canonical: https://highsignal.app/data/records/4f01b51ef25c79f7

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:gamedev)  published 2026-10-19 02:45 ingested 2026-10-20 02:37

[original source ↗](https://www.reddit.com/r/gamedev/comments/1x9li7o/a_pragmatic_view_on_the_use_of_ai_in_game/)

## retained text



```
Earlier today I saw this controversial topic about AI, but I've noticed something weird about the discussion: people seem way more upset when AI is used to generate art, music, or other assets than when it's used to write code.

As an indie dev and programmer, I find this hard to understand. Both programming and art take years to learn, both require creativity and problem-solving, and both take skill to do well. So why is using AI for one often celebrated as a time-saver, while using it for the other can get your game boycotted?

If using AI to make art is wrong, shouldn't we apply the same logic to code?

I get the concerns about copyright, consent, and training data. They're valid. But they apply to code, too. People have been sharing open-source projects for decades, often to help others, provide alternatives, or keep software alive after the original dev moves on. That doesn't automatically mean they agreed to have their work used to train AI models that could eventually replace them.

Then there's AI slop. Everyone hates generic AI-generated images, but with enough competence in programming you can find the same in AI generated code: unnecessary complexity, performance issues, security holes, and bugs hidden behind code that looks correct. 

Others also say we should learn how to draw instead of relying in AI. Shouldn't the same apply to programming? Learning to write good code takes years, too. Yet plenty of devs are happy to use AI and save time. Why is that okay, but using it to explore visual ideas or help produce game assets is somehow different?

So what are we actually arguing for? If using AI for code is just as bad, should we avoid it entirely and give up a potentially useful tool? Or should we allow it everywhere without questioning how it's used?

Personally, neither extreme makes sense to me. AI is a tool, and like any tool, it can be used well or badly. It can help small teams do more with limited time and resources, but it can also produce garbage when people blindly accept whatever it spits out. And whether we like it or not, the industry is already adopting it, specially major studios.

I'm not saying every use of AI is justified, or that copyright, consent, and the impact on workers don't matter. Those are real issues. But there's a difference between criticizing how a tool was trained, how a company uses it, or how someone relies on it, and condemning a developer simply for using it.

At the end of the day, I think what matters most is the human intention behind the work. There's a difference between using AI to help bring a specific vision to life and generating a bunch of assets with no real direction. The same goes for code: using AI to explore solutions and then reviewing, testing, and refining them is very different from blindly pasting generated code into your game.

The tool shouldn't replace the creator's judgment. It should help the creator realize their vision.

So why should we judge someone more harshly for using AI to help create the pixels in their game than for using it to write the code that makes those pixels move?
```



document fetched 2026-10-20 00:26 · canonical https://reddit.com/r/gamedev/comments/1x9li7o/a_pragmatic_view_on_the_use_of_ai_in_game
