A r/gamedev essay argues the community’s reflexive anti-AI stance is becoming a career liability. The author concedes the legitimate concerns — copyright, consent, disclosure, quality — but insists blanket rejection is not a serious response to a tool already embedded across the industry.
- AI is already used across software development, production, documentation, prototyping, testing, research, support, and localization — not just art.
- The questions that matter: where does AI genuinely save time, where does it fail, what should never be shared with a model, how do you verify generated code, what uses require disclosure?
- Cites Linus Torvalds: “AI is a tool, just like other tools we use. And it’s clearly a useful one” — useful, but capable of embarrassing mistakes and extra work.
- Historical pattern: engines, asset stores, visual scripting, and procedural generation all faced “this lowers standards” criticism; each one made human judgment more valuable, not less.
- AI literacy includes skepticism and security awareness — “mindlessly copying generated output is not expertise.”
- The people who win are those who can direct the tool, evaluate results, and stay accountable for what ships.
The essay’s sharpest claim: producing became easier while producing something good stayed difficult, so skilled judgment became more valuable. Worth noting the author is a developer-relations lead for Bezi, an AI agent for Unity games — the thread’s commenters flagged that conflict of interest and pushed back hard.