正在加载视频...
视频加载失败
Everyone's talking about vibe coding without looking at code. I was skeptical. I decided to give it a shot on a challenging problem and was blown away by what I could accomplish in 8 hours. I'm not skeptical anymore, but I also do NOT think it kills SaaS Notes:... show more
49,184 次观看 • 10 个月前 •via X (Twitter)
48 条评论

I disagree so heavily with your SaaS take. For many services (like in the 5-20/mo range), I find 1-2 features interesting, but the prices are high for all the useless garbage you don't need. Guess what LLMs can do in an evening these days. Exhibit A, btw:

What I'm saying is I don't think it categorically kills SaaS. There's a lot of trivial little tools out there that I don't need those are going to be killed. So definitely the bar is raised, but I don't think it's raised so insanely high that it kills the entire category. I think there is a lot of value that people can provide by making things really good and really polished for specific use cases and maintaining them appropriately.

Yeah, the calendar sync thingy, that is dead for sure.

Also, wow they're charging $50/month LMAO! If they charged like $20/year, then I might still pay for it. Honestly, if it is reliable and good.

it is 50/year and they do it "properly" with azure APIs. but the swift script on my mac was like 50 LOC or so and no work (for me)

Swift scripts are so cool. Also, the apple shortcut thingies are underrated as well.

I used @ampcode for this. Used about 700k tokens and 25 different threads. Had three of them going in parallel at the same time.

Exactly It’s been trivially easy to make a sandwich at home for a long time Doesn’t stop you from buying one made by someone else

I couldn't help but think about what the counter analogy would be. 🤣 Someone might say the analogy is like having a Star Trek replicator. You would never buy a sandwich again. The truth is definitely somewhere in the middle. What I was trying to say is SaaS as a category definitely not dead, and lots of things produce non-trivial benefit beyond just the code

That’s fair re the replicator as an extreme Tbh even then you can see people holding up the line at the machine asking for recommendations on what to order. And some enterprising person changing for that.

Yeah true you would still have to prompt the replicator and there would then be prompt marketplaces and such

I decided to transfer the repo (still public) to my friends at AnswerAI. Even though I vibe coded it with public information only, it still superficially appears as clone of an existing product my friends are working on. As I stated in the video, it was purely a vibe coding experiment to see what would happen implementing something I think is really cool. This way, there isn't ambiguity - and you can still view the code there. I even published my @AmpCode threads in the repo in the _threads/ folder Link to repo:

Awesome. It worked really well for me. I tried it for looking at data from one feature and taking notes on what it did poorly. It created really nice widgets for exploring. Super convenient. Now I want to go make more personal tools for fun :D

I don't think SaaS is dead. It's going to be unbundled. We're entering the era of the Headless SaaS. A good API is now worth a lot more than fancy UI with rounded corners.

⬆️ competition ⬇️ margin

Missed opportunity for xq7... should have named it x6-7 😀

Haha

I’m curious what your thoughts are on vibe coded software evals Like it feels like unit/integration tests aren’t a complete solve So what’s the ai eval perspective on evaluating / scoring / grading / improving code you haven’t read? “Look at the code” may also not be the right pace layer 🤔

I don't know that explaining things through analogies is right (I usually do not like to). But, the analogy here would be evals == using the software && testing

what problem did you tackle with vibe coding, curious about the use case

??? That’s what the post is about

Naively we think the value of a SaaS tool resides in the code.

A lot of SaaS is also domain expertise and sales right? I think more and more software will be personalised, SaaS is personalising it to a larger org and selling trust and support Current Vibes does allow me to build something like this quickly though!

I do not look at code much, either. If there is one thing coding agents are best at it's analyzing the existing codebase. I'd argue they are much better at this than at generating new code, e.g.: - document the existing codebase (e.g., authentication[.]md, permissions[.]md, xss[.]md, performance[.]md, cron[.]md) - compare the codebase with that documentation (regularly) - find all ways [a role] can get unauthorized access to [data/feature/organization] - find opportunities to improve the performance in [edge functions/ route/component] - or more focused, e.g., "find all views where we fetch data that is never displayed or used" - go through every OWASP 10 recommendation It's about trust. I learned to trust those prompts just as I would trust expert humans.

from skeptic to shipped

You can edit your base claude .md so it avoids the behavior you don’t like. You can also only have it do one step at a time and work off a plan. ♻️/clear, cat the plan, do one step, update the plan, then stop

vibe code szn, real unlocks

Your eight‑hour breakthrough shows how vibe coding can unlock hidden efficiency.

People might not build EVERYTHING for themselves, but enough people will compete and create things that people want and drive the prices down to the minimal equilibrium which will not sustain current SaaS margins, so there'll be SaaS, but it'll be hard to make money from it.

I think fundamentally, across whatever domain, you still need to know how to solve the problem you're trying to solve with AI and move past the 'papercuts.'

Vibe-coding can one-shot SaaS, if many people are doing it as a team.

That's a great point about not letting the "vibe" overshadow the actual code implementation.

> Most importantly, I don't think this kills SasS at all. Even if I can create software that replicates some of my favorite features, there is an insanely long tail of paper cuts and features I don't want to manage. Exactly. Though it will change SaaS for the better.

Vibe coding is a toy that influencers play with to impress and gain views. Real coders don't use it except to make in-house utilities. There are far more effective ways to write code with AI.

Absolutely the end of Saas, but it will take a few years. We are still way early. Every business with positive cash flow will begin building there own, optimally designed web apps. There future will depend on it!

Just tried it? Damn....

DO NOT do that on real apps, if you end up in an audit and that's what you have to say, you are cooked

Curious if you've tried claude code (Opus 4.5) to be able to compare the experience?

That's exactly what's being used here.

I thought you said it was ampcode?

Oh i misread what you wrote, it's using opus in a different harness. But Yeah, I don't know it would probably work too. I just like Amp!

Yeah no problem, you even had me worried that ampcode could just use claude code as a "sub-harness:. I'm very interested to see if the "harness" has an impact vs the model itself

watching the diffs is the move. let it run blind and suddenly you're debugging mystery code at 2am

vibe code or die coding

vibe code szn hits different

you don’t think agents will proactively maintain and update the app 24/7?

These tests / tests-as-skills are, imho, the absolute core to having a good experience building things. No big long range plan; keep the myriad potential sources of variance to a minimum by articulating clean features and tests stepwise.

i see what you mean now
