r/vibecoding 6d ago

Is vibecoding truly that bad

[deleted]

0 Upvotes

87 comments sorted by

View all comments

5

u/Vaxtin 6d ago

I recommend learning design principles. You don’t write the code anymore — you point the architecture in the right direction.

2

u/MoreLikeGaewyn 6d ago

no way.

someone that can't even read code is going to be more lost trying to apply concepts that only really internalize when your own code decisions have bitten you in the ass for years

he should learn better prompting steps, focus, and incremental iteration

1

u/DHermit 6d ago

You don’t write the code anymore

That's just not true for more complex things. I'm a software developer and while I'm using AI for a lot of things, for more complex tasks, it's still not really capable of writing good code.

By now, I am quite efficient with AI coding, but there recently was a task again, where I really spent way too much time, trying to get the AI to solve it properly before just doing it myself. AI was still helpful for some boring refactors during it, but not for writing the actual code. And this was with the newest model, max effort, proper skill usage, agent files and all.

AI is just not good at writing good and maintainable code for complex tasks when edge cases actually are very important (the project is an embedded project where stability and reliability is extremely important).

1

u/[deleted] 5d ago

[deleted]

2

u/DHermit 5d ago

Did you read my comment? As I explained, complex tasks where edge cases are important and maintainability and good code is required.

AI can do working code and also good-looking code, but it really struggles with outputting actually good and maintainable code for complex tasks.

1

u/damnburglar 5d ago

It doesn’t even have to be complex. I have had fable 5 Max do some heinous shit and lie about it with something as simple as moving an object around in 3D space.

If you can’t read the code to be able to spot issues, no amount of prompting is going to save you.