There's a popular narrative on social media right now that AI can build software so quickly and cheaply that SaaS is dead (or will be soon).

Why pay for Linear when AI can build a project tracker in an afternoon? Why pay Stripe $30k/year when you can vibe code your own billing system in a weekend? The cost of building software has collapsed to near zero, therefore the value of selling software has collapsed to near zero. QED, SaaS is dead.

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?

AI and no-code tools are evolving insanely fast right now. Every few weeks there s a new tool that changes how quickly you can go from idea to product.

I ve been experimenting a lot with different vibe coding platforms lately, trying to find the right balance between speed, control, and flexibility. What s surprised me most is how far you can go today without a traditional engineering setup.

For context, I recently built @Sendrise , an all-in-one cold email outreach platform, using a no-code + AI stack. I used @Lovable for building the product flows and UI, combined with AI tools for writing, automation, and logic. What started as an MVP quickly turned into a fully working product with lead management, campaigns, CRM, and analytics.

What are your top tricks or techniques when building apps and other digital experiences with AI?

The foundation of any successful collaboration, whether human or digital, is mutual understanding and shared context. When onboarding a new developer, you provide essential information about the project's architecture, technology stack, coding conventions, and goals... we can call it "vibe coding" all we want, but to be effective we need more than just vibes.

Hey everyone

No CS background. Started vibe coding 3 months ago.

16+ hours daily. 15 billion tokens later I'm still learning.

I was using a Claude Code leaderboard service made by another dev.
Submitting my daily stats became my end-of-day ritual. It was my fuel for vibe coding.

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?

Every vibe-coding session starts the same:

Here s the context again
Here s what I already tried
Please don t repeat this

That friction killed my flow, so I built Blocpad (CLI).

It keeps context with the project, not trapped in chat history tasks, decisions, notes, all local.
AI reads the state. No re-prompting.

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 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?

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