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.
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
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.
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?
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.
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.
Is anyone else here documenting their vibecoding journeys from ideation to launch? I'm especially interested in process & workflow description, pivots & fails, and lessons learned.
