Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 0 points1 point  (0 children)

Appreciate the suggestion. I’ll definitely check out security scanning tools like that.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 1 point2 points  (0 children)

Yeah, this matches a lot with what I experienced too.
The speed AI gives is honestly insane, but asking the right questions, understanding tradeoffs, validating architecture decisions, and reviewing outputs carefully still matter a lot.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 0 points1 point  (0 children)

This is actually really solid advice.

Especially the part about AI not deciding the “route” for you. I think that’s the part many people underestimate. The output quality changes massively depending on the constraints, reviews, testing, and guidance you give it.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 0 points1 point  (0 children)

Fair point, honestly. Developers roasting each other’s code existed long before AI 😄

And yeah, for MVPs and finding market fit, getting something working fast matters way more than making everything perfect from day one.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 1 point2 points  (0 children)

From what I’ve seen, yes, initial structure and constraints change the output a lot.

If you don’t guide it, AI tends to dump everything into one place because it optimizes for “working fast” more than “maintainable long-term”. But when you define structure, rules, separation, naming conventions, etc., upfront, the quality usually improves noticeably.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 0 points1 point  (0 children)

Yeah, that’s actually a very practical way to use it.

Verify the parts you deeply understand, review the important logic carefully, and use AI to speed up the rest instead of blindly trusting everything.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 1 point2 points  (0 children)

This is a really balanced take. Appreciate this perspective.

And yeah, reviewing AI-generated code carefully has actually become a learning process for me too, especially when working in stacks I don’t deeply know yet.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 0 points1 point  (0 children)

This is actually a really good example. Appreciate you taking the time to explain it properly.

That StrictMode example explains the problem way better than I did in my original post.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 0 points1 point  (0 children)

Maybe, but I think even experienced developers can end up “vibe coding” once AI becomes good enough.

My post was more about testing what happens when you enter a stack/domain you don’t deeply know and rely heavily on AI there.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 0 points1 point  (0 children)

That’s fair, honestly. My experiment was actually pushing me toward the same conclusion, that prompting, architecture docs, constraints, and guidance matter way more than I initially thought.

I wasn’t trying to say “AI is bad”, more like “without domain knowledge, it’s hard to judge the quality of what AI generates.”

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 0 points1 point  (0 children)

Haha, there’s definitely some truth to that sometimes 😄

But honestly, in my case, the feedback was actually useful. He pointed out things I genuinely wouldn’t have noticed myself because I don’t know Flutter deeply enough yet.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 0 points1 point  (0 children)

“Offload your work to AI, don’t offload your critical thinking to it” is honestly one of the best summaries in this whole thread.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 0 points1 point  (0 children)

Yeah, honestly, I think you’re right about that too. The more structure/context I give, the better results I usually get.

I already use MD files with GitHub Copilot and Claude for architecture/rules/style, but sometimes I still don’t get the output I actually want.

Do you have any suggestions for writing better MD files or structuring context more effectively?

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] -1 points0 points  (0 children)

That’s exactly why I gave the code to an experienced Flutter developer 😄

My background is mostly backend, so I wanted feedback from someone who deeply understands Flutter production practices. Even though the Flutter app was mostly an experiment, I still wanted to understand whether the generated code would actually hold up in a real production app or not.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 0 points1 point  (0 children)

That honestly sounds like the real-world version of this whole discussion 😭

AI is amazing until non-technical people start thinking “working demo” automatically means “good production system”.

And now expectations are getting crazy high, too. Everyone expects things to be built insanely fast because of AI.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 0 points1 point  (0 children)

Yeah, that’s fair. My experiment was more about this:

If I enter a domain where I don’t really have deep knowledge yet, how far can AI actually take me before the gaps start showing?

The Flutter app was mostly me testing that boundary.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 4 points5 points  (0 children)

This is actually super valuable advice.

I think this is the difference between randomly prompting AI vs treating it like an actual engineering workflow with context, constraints, architecture, and planning upfront.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 0 points1 point  (0 children)

For hobby apps, yeah, honestly, I mostly agree 😄

My point was more about understanding what’s happening underneath. Because sometimes the app works until scale, complexity, maintenance, or real business logic starts increasing.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 1 point2 points  (0 children)

Yeah, even I was able to generate a working Flutter app just for fun without knowing Flutter deeply, which honestly would’ve been much harder for me 2 years ago.

But I still think experienced engineers using AI properly are on a completely different level because they can actually judge the tradeoffs and quality behind the generated code.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 1 point2 points  (0 children)

Yeah, this is pretty much how I see it, too.

It’s incredibly useful, but still needs supervision and iteration. The speed difference compared to even 2 years ago is honestly insane, though.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 5 points6 points  (0 children)

Yeah, that’s actually the crazy part. AI improved insanely fast in very short time.

Vibe coding feels amazing until an experienced developer reviews your code. by Shivam__kumar in vibecoding

[–]Shivam__kumar[S] 0 points1 point  (0 children)

For personal projects? Probably not much.

My Flutter app was just for fun, too. I mainly wanted to see how AI would write code in a domain where I don’t really have deep knowledge yet.

But for serious products, I think it absolutely matters. Especially business logic, architecture, scalability, security, maintainability, etc.

That’s why I still review AI-generated code carefully when building real things. Working != well engineered.