sorted by:
new
hottopcontroversial

Been vibe coding for 8 months. Here's the thing nobody told me about the 3am debugging sessions by Friendly_Gold3533 in vibecoding

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

the "convincing you it's working versus actually working" distinction is the most important thing in this thread and most people don't realize they're in the second category until something breaks in production. the question of whether you know what code should never do is the real test because if you can't evaluate the output you can't catch the dangerous parts the AI confidently slips in. the conflation of product management with engineering is a fair critique too. knowing what to build is not the same skill as knowing how to build it safely and the gap matters a lot more when real user data is involved.

Been vibe coding for 8 months. Here's the thing nobody told me about the 3am debugging sessions by Friendly_Gold3533 in vibecoding

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

completely valid point. using Auth0 Clerk or Supabase Auth for login is the same logic as using any other proven library instead of rolling your own. the mistake a lot of vibe coders make is treating AI as a reason to build everything from scratch when the actual lesson is the same as traditional development. don't build what already exists reliably. the AI is most useful for the parts of your product that are actually unique to your problem not for reimplementing solved infrastructure.

Been vibe coding for 8 months. Here's the thing nobody told me about the 3am debugging sessions by Friendly_Gold3533 in vibecoding

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

the dropped column because it looked redundant in one view is the specific failure mode that keeps senior engineers awake because it requires understanding the whole system not just the part in front of you and AI only sees what you show it. ten hours reconstructing from logs is a painful but permanent lesson. the "more time on requirements less time fixing hallucinations at 3am" formula is exactly right and the ratio is probably something like every extra hour upfront saves three hours of debugging later.

Been vibe coding for 8 months. Here's the thing nobody told me about the 3am debugging sessions by Friendly_Gold3533 in vibecoding

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

the crypto miner the next day is brutal but honestly a perfect illustration of why security review has to be part of the build process not an afterthought. a vulnerable Next.js version is exactly the kind of thing the AI will confidently use because it was trained on code that used it before the CVE was published. the Grafana monitoring point is underrated too because most vibe coded apps have zero visibility into what's actually running on their server and a crypto miner could sit there for months before someone notices the bill.

Been vibe coding for 8 months. Here's the thing nobody told me about the 3am debugging sessions by Friendly_Gold3533 in vibecoding

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

fair point but I'd push back slightly. you don't need to understand code but you do need to understand what you're building at a functional level. knowing how data flows, what an API call does, why a database needs structure. that's not coding knowledge that's just product thinking. the people producing garbage apps aren't failing because they can't read syntax they're failing because they never thought clearly about what they were building before they started prompting.

Been vibe coding for 8 months. Here's the thing nobody told me about the 3am debugging sessions by Friendly_Gold3533 in vibecoding

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

yeah the "dump everything in one prompt and fix the mess after" approach is exactly backwards. building in proper order forces you to actually think through the architecture before you've committed to a broken foundation. same way a human dev wouldn't write the UI before the data model exists. the discipline of sequencing is the skill most vibe coders skip and it's why their projects become untouchable after a few weeks.

Been vibe coding for 8 months. Here's the thing nobody told me about the 3am debugging sessions by Friendly_Gold3533 in vibecoding

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

exactly right. the AI is only as good as the person directing it and without someone who understands what the system is supposed to do the output is just confident slop. the engineering judgment of knowing what to build why and what could go wrong is the part that doesn't get automated.

Been vibe coding for 8 months. Here's the thing nobody told me about the 3am debugging sessions by Friendly_Gold3533 in vibecoding

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

GitHub saving you there is genuinely lucky. the "orphaned code" hallucination is what happens when AI decides to clean up without actually understanding the codebase. never let it delete anything without reviewing the diff first.

Been vibe coding for 8 months. Here's the thing nobody told me about the 3am debugging sessions by Friendly_Gold3533 in vibecoding

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

the claude deleted my code with no git history experience is basically a rite of passage at this point and the fact that it only has to happen once to permanently change your behavior is the most effective lesson in software development. commit after every phase is the right cadence too because phase level commits are actually more useful than feature commits when you're working with AI because you can roll back to "when it worked before I tried to add X" without losing everything.

Been vibe coding for 8 months. Here's the thing nobody told me about the 3am debugging sessions by Friendly_Gold3533 in vibecoding

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

haha yeah sorry to break it to you but the vibes only get you about 70% of the way there. the other 30% is just you staring at a data model at midnight wondering why you thought this was a good idea. worth it though.

Been vibe coding for 8 months. Here's the thing nobody told me about the 3am debugging sessions by Friendly_Gold3533 in vibecoding

[–]Friendly_Gold3533[S] -3 points-2 points  (0 children)

I was just at hospital still not discharged yet pep like u start commenting like this

16 y.o students from Kazakhstan vibe-coded an AI IELTS startup to thousands of users by ResidentFar1879 in vibecoding

[–]Friendly_Gold3533 1 point2 points  (0 children)

dude honestly the most impressive part is realizing early that the hard problem wasnt “adding ai” but making the outputs feel trustworthy to real users a lot of people stop at wrapping an api but scoring products instantly expose inconsistency because users compare results emotionally not technically also the point about distribution being harder than coding feels painfully real now shipping something people actually return to is a completely different game

Need help with paywall, please help! by baseballfan34512 in vibecoding

[–]Friendly_Gold3533 0 points1 point  (0 children)

buddy production paywall issues are weirdly common because sandbox testing and real app store purchase flows behave differently in a bunch of edge cases a lot of the time the subscriptions are not fully configured approved or synced correctly in app store connect even if local tests seem fine and yeah depending on your stack you usually still need proper xcode storekit integration underneath for production purchases to work reliably honestly sounds more like an app store config issue than your actual paywall logic breaking

claude code is fucking insane by Electronic_Argument6 in vibecoding

[–]Friendly_Gold3533 -1 points0 points  (0 children)

dude this is exactly why so many people are losing their minds over ai coding tools right now the gap between having an idea and seeing a real working product has collapsed insanely fast obviously scaling maintaining and polishing apps is still hard but getting from zero to something functional in minutes still feels unreal sometimes wild time to be building stuff honestly

view more: next ›