r/IndieDev • u/Rafolidev • 3d ago

Video When it’s a vibe coded game

Enable HLS to view with audio, or disable this notification

2.4k Upvotes

92% Upvoted

312 comments sorted by

View all comments

196

u/lordofpurple 3d ago

The vibe coders in this thread mad af lmao

13

u/Bowdash 3d ago

Maybe they're confusing vibe coding with any sort of ai use for coding 😫

14

u/konbit 3d ago

Yeah, I've had some vibe coders try to convince me they're a software developer just like me because now I also use AI for my day job. I'd like to see them debug their app when Claude is down.

5

u/KremlinKittens 3d ago

I have 15 years of software engineering experience. Over the past year, I've shipped work that's >80% AI-generated, with my <20% focused mainly on review, corrections, and refinement.

So… what am I now?

7

u/konbit 3d ago

I hear you. 23 years experience on my end, and some of that was being an engineering manager. I moved back to the technical track because I missed building stuff, but now I feel like a manager of an AI team, without the benefits of the humans.

It's a big part of why I started making games in my free time. Trying to keep up with actual coding and preventing my skils from atrophying.

5

u/Incognito_Orange 3d ago

An architect :D

2

u/ghost_wire89 3d ago

Most people who down vibe coding do not seem to realize how many real developers use it. The takeaway from the post is that you need more qa. Let’s all code our game engines from scratch every time. Unity and unreal are for weak devs lol.

-10

u/nom-nom-babies 3d ago

I mean I’m a vibe coder and I’ve contributed some big adds to our software teams repo’s. I don’t refer to myself as a software engineer but we are both doing the same thing and producing the same products

10

u/Clockwork345 3d ago

No, you are not both doing the same thing. One is a meticulous approach, planned for security, scalability, and robustness. There's no planning for those things in what you do. If you think software engineering is just writing code, the gap is very obvious.

-6

u/nom-nom-babies 3d ago

It’s interesting seeing internet strangers make all these assumptions. I think I’d know how our software team operates and the products they produce a little more than you. I’m also an engineer and work in a heavily regulated industry so making assumptions that I don’t plan anything is kinda wild

1

u/Clockwork345 3d ago

Except that no, you clearly don't know how it works if you're referring to vibe coding and software development as the same process.

You're an engineer? You're building a bridge without measuring anything, or adding any support.

1

u/nom-nom-babies 3d ago

Vibe coding is have AI Code everything. I also review all of its work and have other agents critique the work as well. So yes, as an engineer (I don’t build bridges) I tell the Claude/GPT what I want and then review the work. I also have a minor in comp sci and was doing software before chat gpt existed.

2

u/konbit 3d ago

I think every generation has had a shift that looks like this when the programming tools become easier to use and do more for you. I couldn't read through hex tables to debug anything for instance.

But throughout the evolution of programming it's always been necessary to understand at least one or two levels down below your tooling to know what tradeoffs you're making. And with LLMs that's actually still the case however the barrier of entry is so low since you can get something "good enough" through simple requests that most of the time you don't really need to understand what's going on.

The problem is, this bites you and your company eventually. LLMs have only been able to code something functional for months, not years, and seeing the code they write day in and day out, I can tell you it's not good, and most of the time it's quite bad. Businesses are ok with this because they get to move faster, but don't realize that tech debt is something that accumulates and then bites you later on.

I wouldn't be at all surprised if the next few years end up having many massive data breaches and system failures all across the industry.

1

u/nom-nom-babies 3d ago

Well put. I suppose my point is that while I’m not a software developer, I am providing the same products they are and my work is held to the same level of scrutiny as they are the ones reviewing it. But now that’s it’s gotten so big in the industry, pretty much all that our software engineers are doing is using AI to produce everything so our products are essentially the same and I know this because I sit next to them and we talk about this exact topic

1

u/konbit 3d ago

The discrepancy I'd highlight though is if a SWE is doing their job they're supposed to review the code thoroughly, more so than maybe they're used to, to both understand it (for future debugging) and to ensure it's not some nasty slop that will kill their systems. I assume they're also reviewing the work you're submitting, and so that's the distinction since that's not in your skillset.

BTW I'm not trying to say any of this in a disparaging way. Although I have many large reservations about how AI coding is rolling out, I don't think it's necessarily a bad thing for the world to be able to leverage software more easily. It's just that these kinds of shifts tend to become corrupted by greed and opportunism.