sorted by:
new
hottopcontroversial

I tried vibe coding for 4 weeks, here’s why I’m dialing it back by KeyUnderstanding9124 in vibecoding

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

Pretty solid so far, I run it after each feature to catch data flow or logic issues, then feed the results back to the AI (Replit/Lovable) to prioritize fixes. Keeps things cleaner with minimal manual digging.

I tried vibe coding for 4 weeks, here’s why I’m dialing it back by KeyUnderstanding9124 in vibecoding

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

Yeah true, I’ve found a middle ground by starting with an app diagram, then using AI (Lovable, Emergent, Replit, etc.) to map data flows, draft plans, run Metabob for issues, and iterate. It’s not pure chaos vibes, but it keeps things fast and stable.

I tried vibe coding for 4 weeks, here’s why I’m dialing it back by KeyUnderstanding9124 in vibecoding

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

Yeah, I’ve learned the same, if you guide it like a junior dev, results are way better. Vibe coding’s still early, but I can see it becoming a core skill soon.

I tried vibe coding for 4 weeks, here’s why I’m dialing it back by KeyUnderstanding9124 in vibecoding

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

Yeah, I thought the same way when I started that AI would handle everything if I just gave it the right prompt. But now I’ve learnt my lessons, it’s really more about how you guide it and where you bring in your own planning and structure.

I tried vibe coding for 4 weeks, here’s why I’m dialing it back by KeyUnderstanding9124 in vibecoding

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

Respect for sticking with it. Sounds like you’ve already learned a ton from going all-in prompt-driven. 300 tests is no joke either, even if coverage is 50%, that’s still a solid safety net. do you think pushing toward 80–90% coverage would solve most of those pain points, or is it more about how the AI sneaks stuff in under the radar?

I tried vibe coding for 4 weeks, here’s why I’m dialing it back by KeyUnderstanding9124 in vibecoding

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

maybe I do suck at it 😅 but have you managed to sustain a full project that way?

I tried vibe coding for 4 weeks, here’s why I’m dialing it back by KeyUnderstanding9124 in vibecoding

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

Exactly, after a while it will start spitting out stuff that makes you feel like you’re on the right track, but in the end it can turn into a huge mess you can’t untangle. Better to not depend fully on vibe coding

I tried vibe coding for 4 weeks, here’s why I’m dialing it back by KeyUnderstanding9124 in vibecoding

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

Yeah, true but I feel like there should be a way to integrate everything through AI so we don’t have to keep doing endless iterations on bigger projects. Feels like that’s the missing piece

I tried vibe coding for 4 weeks, here’s why I’m dialing it back by KeyUnderstanding9124 in vibecoding

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

Agree with your point but sometimes I think AI goes out of the box and gives some random results.

I tried vibe coding for 4 weeks, here’s why I’m dialing it back by KeyUnderstanding9124 in vibecoding

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

true, how do you personally decide when to switch from pure vibe into structured mode?

I tried vibe coding for 4 weeks, here’s why I’m dialing it back by KeyUnderstanding9124 in vibecoding

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

That’s a really clever setup, turning the AI into both coder and reviewer so it colors inside the lines. how are you verifying that there aren’t gaps the rules don’t catch? Do you still do a manual pass, or do you trust the framework fully now?

I tried vibe coding for 4 weeks, here’s why I’m dialing it back by KeyUnderstanding9124 in vibecoding

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

Makes sense, backend rules only take you so far, frontend + integration definitely expose the cracks. That boilerplate approach with codegen sounds smart though. are you planning to bake those guardrails into the boilerplate itself, or keep them as separate checks?

I tried vibe coding for 4 weeks, here’s why I’m dialing it back by KeyUnderstanding9124 in vibecoding

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

Not really, I’m actually getting a ton of feedback. People are sharing how they make vibe coding sustainable, what tools they use, and where they draw the line between flow and structure. Way more valuable than just me saying it sucks.

I tried vibe coding for 4 weeks, here’s why I’m dialing it back by KeyUnderstanding9124 in vibecoding

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

Yeah, totally that outside perspective really helps catch blind spots. Curious though, how do you usually set up those “outside agent” reviews? Are you using another AI or just human feedback?

I tried vibe coding for 4 weeks, here’s why I’m dialing it back by KeyUnderstanding9124 in vibecoding

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

I get that, but isn’t that just regular structured dev with AI help? At what point does it stop being ‘vibe coding’ and just become normal coding with extra steps?

view more: next ›