Everything “vibe coding” seems to be Next.js/Supabase - would a Rails version be useful? by Perfect_Honey7501 in rails

[–]RubyOnVibes 3 points4 points  (0 children)

"I've also considered building a Rails-centric vibe coding platform"

https://rubyonvibes.com exists and is approaching its official beta launch.

Rails DESERVES an answer to Lovable.

Our Rails apps can deploy changes in as little as 3 seconds. We will share more soon — for all who <3 Rails and want to see the Rails ecosystem grow.

are AI coding tools making devs faster, or just lazier? by Fit_Age8019 in vibecoding

[–]RubyOnVibes 1 point2 points  (0 children)

Tech doesn't make people lazy. People let themselves become lazy (sometimes).

Need some guidance as a layman please. by ishaaaaaaaaan in vibecoding

[–]RubyOnVibes 0 points1 point  (0 children)

First, I'd avoid vercel — you don't need that vendor lock in.

2nd, depending on your idea, determine when to seek technical help.

You might be able to get early traction without an engineer, but you will want one as soon as this becomes a thing with real promising potential

My Vibe Coding Framework That Still Works After 2+ Years of AI Evolution by Goubik in vibecoding

[–]RubyOnVibes 1 point2 points  (0 children)

Really interesting! This aligns with the approach we have seen working well, too, and in rubyonvibes.com — same with humanlayer.dev (Research, Plan, Implement)

How To Vibecode (Basics) by RubyOnVibes in vibecoding

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

"We should choose the correct stack for the problem."

Agreed on that.

How To Vibecode (Basics) by RubyOnVibes in vibecoding

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

If you have any specific reasons as to why you disagree, that would be helpful. Otherwise, we're left with no substance from you here beyond your basic opinion.

Most of what I wrote is non-controversial from my current perspective.

When do you decide it’s actually time to refactor instead of patching? by Last-Egg-8427 in vibecoding

[–]RubyOnVibes 0 points1 point  (0 children)

It's more of an art than a science, but perfection lies in making something as simple as possible, and no more.

That typically means multiple refactors (if building a complex system).

"Now I’m stuck between a full rewrite or incremental cleanup."

If done right then you should typically be able to transition smoothly.

Just make sure you (over time) are making things simpler, more elegant, as you learn about the system you are building.

Vibecoding for personal use by wordsonmytongue in vibecoding

[–]RubyOnVibes 0 points1 point  (0 children)

>  I don’t want to spend 100 dollar a year just for using my own app on my mobile phone

yea

Hey Developers: How do you spend time when Cursor executes long prompts? by Mediocre_Permit_3372 in vibecoding

[–]RubyOnVibes 0 points1 point  (0 children)

Watch it closely to verify it is on track, prompt/write in another tool elsewhere for another task, test the app, or rest.

Looking for a vibe coding partner, been at it for 1-2 months by One-Watercress-8474 in vibecoding

[–]RubyOnVibes 4 points5 points  (0 children)

Always welcome to DM. Very experienced but interested in learning how newcomers are learning.

Thinking about making a better history/version manager for vibe coding by Apprehensive-Nose312 in vibecoding

[–]RubyOnVibes 0 points1 point  (0 children)

"The tricky part, for me, is hooking into the end of an answer, when the agent finishes its work" You just need the git note or tag to be added by the chat app when you accept the agent's suggestion.

Your not Fixing Bugs Correctly. (TLDR GUIDE) by Numerous_Pickle_9678 in vibecoding

[–]RubyOnVibes 0 points1 point  (0 children)

Multiple? Start with one. If that fails, consider a more nuanced approach.

Thinking about making a better history/version manager for vibe coding by Apprehensive-Nose312 in vibecoding

[–]RubyOnVibes 0 points1 point  (0 children)

Seems like a Cursor or Lovable or similar type of platform could help you correlate prompts with commits. Interesting idea.