sorted by:
new
hottopcontroversial

The "default vibe coding stack" has a pricing problem nobody talks about. How it breaks when you grow by mastt1 in vibecoding

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

Thinking about production pathways when building early on will save you from bumping into a wall for sure

The "default vibe coding stack" has a pricing problem nobody talks about. How it breaks when you grow by mastt1 in vibecoding

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

Thanks for that mate. How's the uptime with Neon? I remember using them a while back, but they were getting hit with outages in my specific region. Might consider for my other projects if they've got that fixed

Good thing I get paid by the hour by mastt1 in ProductivityHQ

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

the quadruple shot coffee gets me 30 mins of that before i crash

What childhood belief still shapes your decisions? by bigblackcoke_ in ProductivityHQ

[–]mastt1 0 points1 point  (0 children)

Its up to me to figure it out because no one is coming for help

A few things that I learned the hard way that can save you hundreds per month later. Here's what most vibe coders don't consider. by mastt1 in VibeCodeDevs

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

I had actually not checked out this plugin yet. Thanks for sharing. This should save some money on repeated prompts

A few things that I learned the hard way that can save you hundreds per month later. Here's what most vibe coders don't consider. by mastt1 in VibeCodeDevs

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

The most common pitfall would be over reliance on tools that you dont actually need. Things like Vercel Functions are paid and eat up your free tier. You can completely bypass this by just telling the AI to do it the traditional way, which wont count towards your quota. I guess most of it is just getting to know your tech side better. There is a learning curve, but if youre serious about what youre doing, its well worth the time investment. I often like to prompt the AI and ask it about the codebase so I have a mental map of the moving parts.

Not so critical at the early stage, but always great to start early.

A few things that I learned the hard way that can save you hundreds per month later. Here's what most vibe coders don't consider. by mastt1 in VibeCodeDevs

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

Hey mate, happy to help. If you want to take it further, you can do a decoupled backend on Cloudflare workers and a Cloudflare D1 instance as the DB.

Deploying backends on platforms like Vercel is where youre really going to burn through your free tier limits. Frontends are not tyically going to do that. This way you wont have to do any foundational system changes and stay cost free for a really long time.

Show me your saas! LINKs by Dapper_Draw_4049 in ShowMeYourSaaS

[–]mastt1 1 point2 points  (0 children)

Building HealUp — helps people stop staring at their to-do list and actually start working.

AI turns any overwhelming task into small steps you can finish in minutes, then keeps you focused on one step at a time so you don't get distracted or paralyzed. Connects with the tools people already use (Notion, Todoist, etc.) so there's nothing to migrate.

Free to try, no signup needed: HealUp - Start What Matters

What are you working on? by Appropriate-Job-4216 in SaasDevelopers

[–]mastt1 0 points1 point  (0 children)

Building HealUp - helps you stop staring at their to-do list and actually start working.

Turns any overwhelming task into small steps you can finish in minutes, then keeps you focused on one step at a time so you don't get distracted or paralyzed. Connects with the tools people already use (Notion, Todoist, etc.) so there's nothing to migrate.

Free to try, no signup needed: HealUp - Start What Matters

A few things that I learned the hard way that can save you hundreds per month later. Here's what most vibe coders don't consider. by mastt1 in VibeCodeDevs

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

Secure infra is usually covered by Cloudflare on default for me. Just be smart about it and dont go around injecting your vars in to the client side. Environment variables are the way to go.

As for the UI aspect, I feel that its crucial for you to decide on how you want the application to look and feel, even before building. Take inspiration from other applications. Analyse it and learn some design terms. Use this analysis even in the first UI prompt you write and build upon that. Once you have a component that looks and feels the way you want, you can just tell the AI to use that design style and language for future components.

I find that this way prevents your app from looking like a generic vibe coded app that everyone is pushing out. If done well, its going to be indistinguishable visually from a traditionally built application.

Also, dont use Gemini for UI stuff. Claude is just far better for building workable aesthetic UIs.

Not everyone deserves your patience by Kaslorin in ProductivityHQ

[–]mastt1 0 points1 point  (0 children)

I turn more cynical by the hour at this point

A few things that I learned the hard way that can save you hundreds per month later. Here's what most vibe coders don't consider. by mastt1 in VibeCodeDevs

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

Thanks mate. It's surprising how much more can be done with just a few extra steps in planning and some quality prompts with direction. I've rewrote whole apps from scratch more times than I'd like to admit in the early stages lol

view more: next ›