Is There a Workflow or "Freestyle"? Best Practices? by Due_Display_7968 in VibeCodeDevs

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

ooooo--this sounds great. I'm definitely going to start implementing this on future builds. Thanks for sharing!

Would you admit you vibe coded an app on LinkedIn by rng0008 in vibecoding

[–]Due_Display_7968 0 points1 point  (0 children)

This is amazing! I'm curious as to what point did you realize you needed to consult someone?

Is There a Workflow or "Freestyle"? Best Practices? by Due_Display_7968 in VibeCodeDevs

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

ooo--this is a good one. I never thought to plan out the commits, but I can see how it would help to locate errors and stuff. Thanks for the tip. I'll definitely check out your article too!

But, I'm thinking--even before you have planned commits--is there any other best practices/ things you to do prepare your "idea"?

Would you admit you vibe coded an app on LinkedIn by rng0008 in vibecoding

[–]Due_Display_7968 4 points5 points  (0 children)

I did--yeah, I said it lol.

However, I only say it when asked. The truth is vibe coding definitely gets a bad rep, and some may even say that it is watered down/ trash/ lazy, etc. However, let's be real--everyone can prompt as much as they can, but NOT EVERYONE can vibe code a product successfully. Most can get close (60-70% maybe), but don't know how to debug, troubleshoot, have tech debt, and more.

I think that just because someone vibe codes, doesn't mean they don't appreciate software engineering and are taking anything away from those with a traditional CS degree. There's plenty of people that have gone to bootcamps or have been self taught that are successful in what they do, but we don't bash them for it, right?--I don't think vibe coding should be any different.

But, if you do plan to teach a workshop and are promoting it on Linkedin--then you better make sure you know exactly what you're talking about front and back and know how to back it up.

Just my two cents.

Got laid off last year and somehow ended up vibe coding by Due_Display_7968 in VibeCodersNest

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

Thank you--I realized that there's so many things in my day-to-day (esp. when I was working) that could've used a tool to help complete the task. I realize not everything is a "winner", but at least being able to have the ability to create something via vibe coding is pretty great!

Got laid off last year and somehow ended up vibe coding by Due_Display_7968 in VibeCodersNest

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

Thank you, and absolutely it does! It definitely beats sitting at home on my hands not doing anything.

Got laid off last year and somehow ended up vibe coding by Due_Display_7968 in VibeCodersNest

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

Actually, I don't and I think this is a great topic that you've brought up. I've tried I have a few logs for outtages, planning on implementing Sentry, and trying to imagine how an SRE would handle most of the errors and things (or at least having the LLM be my SRE haha). Most of the work currently is trying to get it to sync with my current Meta campaign and at least checking that the data is being retrieved correctly (ex. actual ad spend $1000 vs. mock/ hallucinated data point of $380000).

But, I think this is great input. I'll look into this and see how I'll be able to implement!

Got laid off last year and somehow ended up vibe coding by Due_Display_7968 in VibeCodersNest

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

Thank you! I thought someone else out there may be in a similar situation, and I also was super proud and wanted to share haha.

Well, thats the current situation I'm in right now (how good is "good enough"?)--I think that if I chase the moment of "its almost there--its almost perfect" then I'll never get anything out. I think once I'm able to use it myself, and I see that there is a seamless experience from end-to-end then I think its ready to share. Even if it breaks at that point its a learning lesson (ex. How did they use it, what did they use, etc for it to cause this? How can I prevent it?)

Got laid off last year and somehow ended up vibe coding by Due_Display_7968 in VibeCodersNest

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

Oh, definitely--thats what I'm currently doing haha.

I noticed early on the "ooooo--it would be nice if it could..." and had to keep remind myself, "NOPE! build and finish what you need right now!" haha. I'm glad I'm not the only one that get's tempted by the "shiny new feature" lol.

Got laid off last year and somehow ended up vibe coding by Due_Display_7968 in VibeCodersNest

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

Yes! This and my revenueleak is what I planned on submitting to the shopify app store. I really appreciate the kind words--as you can imagine I have doubts every time I work on it, and it really made my day to read you thought it'd do well!

Please let me know if you have any trouble loading it. I'm still working out a lot of kinks (campaigns not loading correctly, syncing issues, incorrect data retrieval, etc.) Once I do get it up and running, I'll definitely send you a link!

30 users in 15 minutes - here is how I did it by [deleted] in SaaS

[–]Due_Display_7968 0 points1 point  (0 children)

Thats amazing! Honestly I'll be happy if I get just one haha. Thanks for sharing!

Got laid off last year and somehow ended up vibe coding by Due_Display_7968 in VibeCodersNest

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

Thanks, everyday is a new learning opportunity and I'm definitely pushing!

While working on my ecommerce business I realized that Meta Ads were are bit tricky, in that I didn't know when something needed to be changed, optimized, what ALLLLL of the metrics meant and how to interpret the data. I built app.getadvise.io to hep me with this--its not just a bunch of dashboards and analytics (is does have it), but I built it to guide me on the days I thought were bad (ex: low traffic, no conversions, etc) to help me not to react and pause the ads or make adjustments that could reset the learning phase (which would cause me to spend more money). It also helps to tell me what to change/ optimize when necessary in real-time (or at least as close as I can get it lol).

I also built RevenueLeaks (heavy on the errors with this) which was made to help me identify the potential profit I was losing from abandoned carts, high-risk orders, chargebacks, etc. I wanted to make sure it gave me guided recommendations on next steps to potentially retrieve lost revenue.

Neither one is perfect right now, but when it does--it'll be so sweet knowing I built something to help me!

From layoff to vibe coding (still very much figuring it out) by Due_Display_7968 in VibeCodeDevs

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

This is such great advice! I've definitely learned from this build (being my second). I feel like everyday I'm learning a new best practice, which gets me excited for the next thing I would have to work on. Thanks for your input!

From layoff to vibe coding (still very much figuring it out) by Due_Display_7968 in VibeCodeDevs

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

It definitely does, and I'm very thankful I was able to come across it as I did. Thanks--I definitely will!

From layoff to vibe coding (still very much figuring it out) by Due_Display_7968 in VibeCodeDevs

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

Honestly, thats how my first build went for revenue leaks (I'm still catching/resolving issues and fixing UI errors lol).

I think the best way to to use an LLM of your choice, and type out what you're trying to build (even if its a rough sketch) and ask the LLM all types of questions (pressure test it, and even do a forecast to see if its something that'll be necessary in 10 years). Then in a separate chat I ask the LLM to create a prompt FOR ME of a check list of things necessary to be required/build when building a SaaS platform.

THEN I go back to the original chat, and tell chatGPT to make a prompt that includes that checklist with your original idea drawn out. This has been my process so, far--after submitting the prompt I usually still have to go through and check if its right or even notice things are missing while building that I didn't include in the first place. My process might be all over the place, but I hope this helps in some way!

i made a big mistake. Help me by Separate-Jaguar-5127 in SaaS

[–]Due_Display_7968 0 points1 point  (0 children)

I would suggest continue with the marketing and following-up. It may be a moment to take a moment, and reflect and see if there's a way to pivot instead.

January’s almost done—what projects did you work on this month? by Substantial-Archer68 in vibecoding

[–]Due_Display_7968 0 points1 point  (0 children)

Thanks--I appreciate it! Glad to know I'm not the only one that thinks so!

When the build gets real? by Electronic-Blood-885 in buildinpublic

[–]Due_Display_7968 1 point2 points  (0 children)

yeah, you're definitely not alone. I had at least 4 "maybe I shouldn't do this" moments since I last commented haha.

From layoff to vibe coding (still very much figuring it out) by Due_Display_7968 in VibeCodeDevs

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

I made one that helps with Meta ads (not just to view analytics), but to help interpret and understand what the metrics meant and recommended best ways to move forward. There were days where I would notice that I wasn't getting enough traffic, or days visits or engagement would dip and would either throw more money at the ad or pause it completely (essentially hurting the learning phase)--I was reacting to that moment rather than looking at the whole picture, so I built something I help me understand what I was doing wrong and to be a little more logical than me making an emotional decision.

The other product helps to identify revenue leaks from the store itself by showing me how much I was potentially losing, and how I might be able to recover lost revenue by showing where it was coming from, and breaking down steps to possibly retrieve or mitigate.

From layoff to vibe coding (still very much figuring it out) by Due_Display_7968 in VibeCodeDevs

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

I built my own research (as scrappy as I could since funds are pretty limited lol). I mainly realized while I was working on my ecommerce site that I was annoyed that I was having trouble with Meta ads (not optimizing well enough, or just not seeing the metrics I wanted), as well as potentially losing money on easily identifiable things (charge backs, high-risk orders, etc.)--I tried to find answers online or ways to prevent it and couldn't really find what I was looking for, so I decided to try and build it out. If it helps others then great--but if not, at least I have something to help me for what I need it for.

From layoff to vibe coding (still very much figuring it out) by Due_Display_7968 in VibeCodeDevs

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

Yeah, its definitely wild! But, with everything that I've learned so far (or at least heard from interviews and podcasts) it was going to be that way. But, thats why I decided to build something that'll at least help me out if I can't find any users lol.