Vibe coders: how do you catch bugs before they hit production?
Building my app with AI tools, zero coding background. The magic part - I can ship features in hours. The scary part - I have no idea if the code is actually good.
Right now my "QA process" is:
- Does it work when I tap around?
- Did anything break that worked before?
WIndurf somehow is not doing anything. What's going wrong?
I started with Windsurf IDE and swapped to Cursor IDE.
I returned to the Windsurf IDE and used some of the default MCPs. I am on the free tier using SWE-1 (lite) and started a brand new project. But somehow, it doesn't matter what I do, it always says "running" or "it's taking longer than expected", but nothing happens at all.
I just wanted to get a feel if it's worth it to come back. I didn't want to insert coins yet, I'm not clear if it would be.
So I made a PRD, SRD and was trying to use sequential thinking.
So, any ideas what it is, or is it normal that the free tier doesn't do anything?
How does vibe coding influence the way we build products?
I ve been thinking about how vibe coding building based on feeling, speed, and flow instead of rigid specs changes the product creation process.
Some feedback I ve heard:
Vibecoding AI models with Windsurf
I'm Kevin, founder of EnginifyAI. Over the last 12 months I've been working on a prompt engineering tool. I started off using Bolt but quickly I found myself unable to completely use it effectively. I then tried Cursor and was using it early on but maybe I had the wrong settings as I found myself using all my credits in 2 days. So, I switched to Windsurf, and to my surprise credits were a bit more manageable and it took about 2 weeks before my credits were consumed. Keep in mind that I am new to coding so I spent a lot of time asking questions in Windsurf instead of using my paid subscription to Anthropic.
I'm coding using React/Typescript and Supabase. I have learned that coding is a lot of work, a lot of fine-tuning, and a lot of testing and fixing. The one thing I haven't quite figured out completely is how to fix migrations. Early on I was running SQL scripts directly in Supabase without migration scripts because I found it to be faster. But now Windsurf uses very old migration script references and I find myself fixing the same issues because of an old migration script reference. Any idea how to fix this?
I assume that vibecoding is an experience everyone can enjoy but comes with frustrations about asking the right questions, or being very specific about my requests. I am using Claude Sonnet 4, 4.5 and 4.5 thinking. Are these the best coding ai models for Typescript?
Just an appreciation for vibe coding
I've been vibe coding( @Lovable , @v0 by Vercel ) for a couple of months now & it's such an incredible feeling. What once required specialized skills now happens through simple descriptions.
Breaking free from dependency on designers & engineers for mocks/prototypes has been especially empowering. Great to see this creative autonomy that has fundamentally changed how people build.
What an incredible future we are creating for kids who can create software from sentences.
Building a vibecoding mentor-matching platform in public without dev
I'm Vasyl, and three days ago I couldn't code. Well, today nothing changed lol. It would be great to hear some advice, how you guys as low Cursor credits as possible.
Today I'm 82% done with a web app full-stack mentorship platform.
WHAT IS IT: a mentor-mentee matching web app where professionals can find the right guidance and mentees can connect with experienced mentors in their field.
THE TWIST: I'm building this entire thing with zero coding background, using Cursor IDE + Claude AI, and documenting every single day publicly.
WHERE WE'RE AT (Day 3): - Backend: 100% complete (auth, payments, messaging, reviews) - Frontend: 70-100% depending on feature - Dashboards: Fully functional - One blocker: Database setup (2 hours away) - Launch: ~20 hours of focused work
WHY THIS MATTERS: Not trying to sell you on the app yet (it's not even live). But the meta-story is wild - AI just changed what's possible for non-technical founders. The barrier between "I have an idea" and "I shipped a product" collapsed.

FOLLOWING ALONG: Building in public on X (@VasylK23416) and LinkedIn. Every day. The wins, the bugs, the "why doesn't this work" moments. Launch coming next week. Would love your thoughts, feedback, or just follow the chaos. What was your experience learning to build your first product? #buildinpublic #AI #nocode #mentorship
Vibecoding: I'm cooked
For more than a year now I have been consistently working in a vibecoding format. During this time I have created several unusual solutions and finally decided to start showing them publicly.
These are small research pieces that can inspire and at the same time remain utilitarian.
What’s Your Biggest Pain Point With Code Security Tools?
As devs, we all know the struggle with code security scanners:
Switching between IDE and clunky dashboards to check vulnerabilities
Wasting hours sifting through false positives
Getting vulnerability alerts with zero guidance on how to actually fix them
I stumbled on an IDE extension (ZAST Express for VS Code/Cursor) last week that s amazing for my workflow. The Proof of Concept (PoC) feature is what sold me instead of just flagging issues, it gives runnable snippets to validate the problem, plus clear fixes right in my editor. No context switching, no guesswork, and it s free to start.
I built Iconstack (50,000+ free SVG icons) with Lovable - feedback wanted 🙌
Hey folks
Quick share: I got tired of bouncing between 10 different sites every time I needed a simple arrow or calendar icon. Felt like such a dumb waste of time.
Building our first SaaS and are bootstrapped. What's your hack to keep cursor costs at bay?
I would highly appreciate some information how you keep costs low. What we are now going to do:
Run everything on VMs
Rent A100s through Google Cloud for Startups Program (if they let us do this)
Switch to Haiku
What else can you recommend?