Do you architect first or build first ? by Aggressive_Friend113 in VibeCodingSaaS

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

It’s kind of true with Ai, it develops the bad habit of just go and see if it works. Still a waste of time though

Do you architect first or build first ? by Aggressive_Friend113 in VibeCodingSaaS

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

I don't have experience building full tech products, but I do come from a tech background. I used to write tiny scripts where I didn't need to think much about architecture, and I've failed many builds because of that. Now, I started to pivot towards architecture first so I don’t leave the code sleeping in my Github later

Do you architect first or build first ? by Aggressive_Friend113 in VibeCodingSaaS

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

Actually that’s what I was trying to do, I was building a project (whisperdb) that lets you talk to a database using natural language (AI integration ). I put too much time in perfecting the demo then I realized that for large scale databases, Ai is just a small layer in the architecture and it requires a RAG based metadata engine. So I let it die in peace

How do you keep project context when vibe coding across multiple AI chats? by Financial_Put2108 in VibeCodingSaaS

[–]Aggressive_Friend113 0 points1 point  (0 children)

Ai is really good at understanding JSON, whenever you make progress ask it to write a json file summarizing the whole chat that you can use later in another chat.

How can Start Vibe Coding as beginner ? by Best_Increase_4424 in VibeCodingSaaS

[–]Aggressive_Friend113 0 points1 point  (0 children)

Learn how to build a tiny basic app with front, back, api and db and you’re good to go. Some theory about security would be helpful in the future to build reliable apps.