AI-Assisted coding is not the same as vibe coding
retained text
Context: I've been a game modder and dev for nearly 20 years. I started modding Doom all the way back in 2007. Back then, getting into this stuff was HARD. And I mean really damn hard. Tutorials were scarce, and you often had to piece together information from forums and other scattered sources. It was hell, and I'm frankly stunned that I was even able to do it at all. I'd have absolutely murdered to have the AI tools we have today. Yet, the use of AI-generated code continues to be mocked by many within the gamedev and modding communities, and it simply makes no sense. I see people throw the term 'vibe coding' around a lot, but imo this term no longer means anything because of how overused it's become. And there are three major fallacies I'd like to address specifically. The first is using 'vibe coding' as a general term for any use of AI coding tools. That's a flawed premise because somebody with a general understanding of coding will not use these tools in the same way somebody with no understanding of code would. An actual programmer will plan the general approach in advance and then tell the AI to execute specific tasks. This is utterly different from mindlessly prompting with no implementation strategy in mind. The second issue is this obsession with needing to understand everything. In reality, understanding things at the macro level is usually what matters most. The specifics of individual functions, syntax, etc are much less critical. Wasting time trying to obtain a deep understanding of every little thing is unnecessary and just results in wasted development time. There's also a certain level of hypocrisy here, since even before AI, many coders would simply paste code from other sources without carefully studying it first. The third issue is making false equivalences to other types of AI, such as AI image generation. The reason the 'you didn't create that' argument is valid against AI images is that there's a large amount of non-determinism in the end result. If you prompt an AI to generate an image of a man standing in the rain, it might produce that image, but it will also determine many other details that you didn't specify e.g. his pose, clothing, hair, general scene setup, etc. In contrast, AI-coded game mechanics are deterministic in terms of their intended functionality. If I tell the AI 'I want you to code a health system where the player takes 5 points of damage every time he's hit by a projectile,' the AI will produce the code needed to implement that specific mechanic, and only that mechanic. Sure, the exact details of how the code functions might differ slightly, but the intended in-game functionality remains the same regardless. This is deterministic design. I'm going to be honest. In 2026, not using AI as part of your coding workflow amounts to self-sabotage. It's already mainstream. Those who refuse to use it will eventually become unable to compete.
document fetched 2026-10-21 00:25 · canonical https://reddit.com/r/gamedev/comments/1xapusg/aiassisted_coding_is_not_the_same_as_vibe_coding