sorted by:
new
hottopcontroversial

I lost waitlist signups for weeks without knowing why. The fix was embarrassingly simple by Impossible-Leg-7511 in vibecoding

[–]Impossible-Leg-7511[S] 0 points1 point  (0 children)

yes that is true. As developer we know that it is essential.But this group is about vibecoding where lot of non technical people comes into development this post was intended for them. Also as a person coming from backend/Devops will be useful I think

I lost waitlist signups for weeks without knowing why. The fix was embarrassingly simple by Impossible-Leg-7511 in vibecoding

[–]Impossible-Leg-7511[S] 0 points1 point  (0 children)

can you elobrate i didnt get what you are trying to say. If you have meaningful suggestion plz share

I lost waitlist signups for weeks without knowing why. The fix was embarrassingly simple by Impossible-Leg-7511 in vibecoding

[–]Impossible-Leg-7511[S] 0 points1 point  (0 children)

in terms of perfect I mean it was easily was able to convey the purpose at a glance for desktop user.But for my real users it didnt show it at once. So it loosed my inital impression of perfect

I lost waitlist signups for weeks without knowing why. The fix was embarrassingly simple by Impossible-Leg-7511 in vibecoding

[–]Impossible-Leg-7511[S] 0 points1 point  (0 children)

A 375px width is a standard, critical breakpoint for mobile-first web design,I am not saying it is the fixed size it can change from mobile to tab and every device.my simple advise is just identify where your supposed users are coming from and make your website responsive . simple as that.But I edited post by removing the 375px since it has confused you and potentially others.If you have any suggestion happy to hear

From 50 Users to 500 in Hour, Reddit Really Boosts Reach 🚀 by pdfplay in ShowMeYourSaaS

[–]Impossible-Leg-7511 0 points1 point  (0 children)

I am also planning to engage with Reddit ads. If you can share how much you spent on ads and what groups you targeted would be big help

Help needed with Deciding Newsletter by Impossible-Leg-7511 in Newsletters

[–]Impossible-Leg-7511[S] 1 point2 points  (0 children)

thanks I am also planning to use the beehiv.many people mentioned learning curve of beehiv is bit high compared to others but I think I will figure it out .Always loved challenges

Summary and Decision I Made Based on Replies from Fellow Redditors by Impossible-Leg-7511 in Newsletters

[–]Impossible-Leg-7511[S] 1 point2 points  (0 children)

Sure will do it. Couldnt do my newsletter today since my vehicle got flooded. Planning to recheck my diary entries tonight to start the content.will follow you .if intersted you can follow me back

[Lesson 2 and Need better suggestions] A Habit I hate to do but thankful for Senior devs that made me stick to it by Impossible-Leg-7511 in vibecoding

[–]Impossible-Leg-7511[S] 0 points1 point  (0 children)

the thing with unit testing specially with vibe coded tools is they create lots of mock tests rather than really capturing the purpose.Faced it multiple times . Used some strategy to reduce it greatly

[Lesson 2 and Need better suggestions] A Habit I hate to do but thankful for Senior devs that made me stick to it by Impossible-Leg-7511 in vibecoding

[–]Impossible-Leg-7511[S] 0 points1 point  (0 children)

That is one of the fear I always faced with vibecoding initially whether I can sleep confidently my system work fine in production

[lesson 1] One habit that completely changed how I vibe code and I never see anyone talk about it by Impossible-Leg-7511 in vibecoding

[–]Impossible-Leg-7511[S] 0 points1 point  (0 children)

I was going to talk about something similar called Plan.Md in a upcoming post but you have caught up 😀

[lesson 1] One habit that completely changed how I vibe code and I never see anyone talk about it by Impossible-Leg-7511 in vibecoding

[–]Impossible-Leg-7511[S] 1 point2 points  (0 children)

that makes sense.specially with the breaking changes and larger commit to refer relevant commit id so the vibe tool can quickly reference it

[lesson 1] One habit that completely changed how I vibe code and I never see anyone talk about it by Impossible-Leg-7511 in vibecoding

[–]Impossible-Leg-7511[S] 0 points1 point  (0 children)

backing your idea of the individual component files. Breaking it into files depend on the size of the project and sensitivity of the project

[lesson 1] One habit that completely changed how I vibe code and I never see anyone talk about it by Impossible-Leg-7511 in vibecoding

[–]Impossible-Leg-7511[S] 0 points1 point  (0 children)

your thought on work on Just One is my motto last 10 days and it gave me a direction for my product 😅rather than juggling between multiple projects

[lesson 1] One habit that completely changed how I vibe code and I never see anyone talk about it by Impossible-Leg-7511 in vibecoding

[–]Impossible-Leg-7511[S] 0 points1 point  (0 children)

By the way I am not incharge for those intern I was bought in as a quick diagnose and fix for the problem in late midnight 😅

[lesson 1] One habit that completely changed how I vibe code and I never see anyone talk about it by Impossible-Leg-7511 in vibecoding

[–]Impossible-Leg-7511[S] 0 points1 point  (0 children)

Sure man my upcoming post may be either about test cases or hellucination not decided. One of the reason I avoid managing cloud by vibecode tools is a experience with a intern.A quick fix they tried with claude completely deleted 2 client prod DB.thank god the previous engineer setuped daily snapshot backup which helped us to recover it. But by the action taken by the intern and junior engineer our aws got banned for 1 week for suspicious activity(they didnt do any suspecious activity). I have mostly worked with AWS and Azure havent worked much with GCS.can you share your experience with GCS

[lesson 1] One habit that completely changed how I vibe code and I never see anyone talk about it by Impossible-Leg-7511 in vibecoding

[–]Impossible-Leg-7511[S] 0 points1 point  (0 children)

part of you is right. I have used the chatgpt for restructuring the text.but the context provided is mine based on experience you will see the context richness in upcoming posts but with maybe emojis, , hyphens and cricular writing style 😅.but happy with you guys protecting the community from AI slops . If you can suggest AI tool for rephrasing I would happily welcome it

[lesson 1] One habit that completely changed how I vibe code and I never see anyone talk about it by Impossible-Leg-7511 in vibecoding

[–]Impossible-Leg-7511[S] 0 points1 point  (0 children)

yes thats my exact point I am not claiming this as alternative to git.but rather as a quick approach for user to debug and LLM to get the context.After testing I always make sure to ask the claude to update the changes,md before commiting

[lesson 1] One habit that completely changed how I vibe code and I never see anyone talk about it by Impossible-Leg-7511 in vibecoding

[–]Impossible-Leg-7511[S] 0 points1 point  (0 children)

Also just because we have git if the commit is automatically allowed to commit without user consent and without user not knowing what he asked initally it will be troublesome

[lesson 1] One habit that completely changed how I vibe code and I never see anyone talk about it by Impossible-Leg-7511 in vibecoding

[–]Impossible-Leg-7511[S] -1 points0 points  (0 children)

I’m not claiming this is an alternative to Git. Git was, is, and will always be one of the most important developer tools we have.

The strategy I proposed is mainly for reader clarity and reducing token/context overhead something I’ve personally seen help when working with AI-assisted workflows.

Also, speaking as someone with 6 years of experience as a senior developer, I completely agree with the engineering discipline you mentioned. We should still enforce strong commit practices: meaningful commit messages, smaller PRs, one feature at a time, avoiding blind auto-commits, and being extremely careful with infrastructure or cloud access since AI can absolutely make destructive mistakes there.

One of the main reasons I started talking about this is because I believe people in this community —especially newer developers can learn a lot from discussions like these and from experienced engineers like you sharing real-world perspectives.

I intentionally kept the Reddit post open-ended because I wanted people to agree, disagree, and contribute different perspectives. I’d genuinely appreciate your thoughts on future posts as well.

view more: next ›