60岁的Vibe编码者创建了一个通过Vibe代理和Vibe测试工具实现收入的SaaS。
我们代表一位60岁的父亲，他在与Lovable合作后遇到了麻烦。以下是我们发现的情况：
我们为ScoutQA工作，利用Amazon Bedrock与我们的朋友和同事们一起开发了这个自动化的Vibe测试代理。我想知道是否有人和我们的客户一样，遇到了相同的问题。我们本质上是开发者和质量保证人员，但我们发现很难了解社区对像我们这样的工具的需求。因此，我们想分享一下老年人在使用WordPress进行商业活动和Lovable网站时所面临的困扰。下面是我们客户的一段观点和引用：
“我是一名60岁的Vibe编码者，只在Lovable和ScoutQA上构建SaaS——学习新东西永远不嫌晚。”
我60岁，已经在软件测试领域担任项目经理40年。
不过，我仍然不写代码。
我基本上依靠两样东西来构建我的SaaS：
Lovable来构建 + ScoutQA来测试。
没有IDE，没有CI管道，没有Git差异的墙。我认为年纪大了让我很难学习新工具，但我终于在构建出可以交付的高质量产品上取得了进展。
1. 我实际交付的内容：
我使用Lovable构建完整的产品，而不仅仅是MVP：
- 一个有付费客户的合同管理SaaS
- 一个基础设施管理平台（GG Workspace）
所有这些都是在不接触生成代码的情况下构建的。代码在GitHub上仅作为备份。如果我打开它，对我来说毫无意义。
2. 在使用ScoutQA之前，我的弱点在于反复修改：
- 在Lovable中更改一项内容 -> 随机流程在其他地方崩溃
- 花费数小时点击所有内容，仍然错过问题
现在，使用ScoutQA的工作流程帮助我发现了一个我之前不知道的真正XSS漏洞。它将所有内容组织为项目/网页应用，而不是代码库。这让我更像一个产品经理，而不是开发者。
手动测试就像希望你的网页应用在上线后不会崩溃，而对于自动化测试，我只需点击一个按钮。
我大多数晚上大约花一个小时来构建。这就是我的全部。没有12小时的调试马拉松。
这是我们一位60岁客户的故事，他在英国，我希望你们喜欢。如果可能的话，请随时提供反馈并尝试我们的产品。它基本上是一个无需设置的Vibe测试网站，只需粘贴你的URL，让Scout处理所有的错误，如SEO、功能、性能、导航等……ScoutQA非常适合Vibe编码者、网页构建者、资源有限的独立开发者和测试人员。该产品目前处于免费测试阶段，因此你可以进行尽可能多的测试。
总结：我们的60岁客户无法阅读代码，使用Lovable + ScoutQA交付稳定的、盈利的SaaS产品（他的产品规模较小，客户不多，希望专业开发者能理解他在扩展方面的困难）。像ScoutQA这样的自动化Vibe测试代理可以帮助你减少手动工作的努力，并通过错误修复报告提升你在客户心中的可信度。
查看原文
We represent client who is a 60 year old father have troubles after working with Lovable. Here is what we found<p>We work for ScoutQA and we made this auto vibe testing agent using Amazon Bedrock with our friends and colleagues. I was wondering if anyone had the same pain points as some of our clients have reached out to us on. We're devs and QA people at heart and it's surprisingly hard for us to know what the community would want from a tool like ours. So we would like to share more about the trouble of old people making wordpress business and Lovable website. I'll post below one of the POV and quote from our client:<p>"I’m a 60 year old vibe coder, building SaaS only on Lovable and ScoutQA - it's never to late to learn new stuff"<p>I’m 60. I’ve been working as Project Manager in software testing for 40 years.<p>I still don’t write code though.<p>And I’m making my SaaS with basically two things:
Lovable to build + ScoutQA to test<p>No IDE. No CI pipeline. No walls of Git diffs. I think old age make it hard for me to learn new tool, but it a progress made for finally finish building something that shippable with quality<p>1. What I actually ship:
I use Lovable to build full products, not just MVPs:
- A contract management SaaS with paying customers
- An infra management platform (GG Workspace)<p>All of this, built without touching the generated code. The code lives in GitHub purely as a backup. If I open it, it mean nothing to me.<p>2. Before ScoutQA, my weak spot was back and forth stuck:
- Change one thing in Lovable -> Random flows break somewhere else
- Spend hours clicking through everything, still miss issues<p>Now my workflow with ScoutQA help me caught a real XSS vulnerability I didn’t know about. It organizes everything as projects/web apps, not repos. Kinda lets me think like a product person, not a developer<p>Manual testing is like hoping your web app would not broken after launch, but for automation test, I’m just clicking a button.<p>I build for about an hour most evenings. That’s it. No 12‑hour debug marathons.<p>That is the story of our client in their 60s base in UK, I hope you guys enjoy it and if possible, feel free to give out feedback and try our product. It basically a vibe testing website with no set up, just paste your URL and let Scout handle all the bug like SEO, Functional, Performance, Navigation, etc...ScoutQA is perfectly fit for vibe coder, web builder, solo dev and tester with little resource. The product is in beta free mode so you can run as many test as you like.<p>TL;DR: Our 60 years old client, who can’t read code, using Lovable + ScoutQA to ship stable, revenue SaaS products (his product is small scale with few customers so I hope pro dev would empathize with him about scaling). Automated vibe‑testing agent like ScoutQA can help you save less effort with manual grind and improve your credibility to customer with bug fix report