一种氛围感满满的SaaS产品毁掉了我的团队。
A Vibe Coded SaaS Killed My Team

原始链接: https://cendyne.dev/posts/2025-11-26-a-vibe-coded-saas-killed-my-team.html

## 公司转型与对“氛围编码”平台的担忧 作者的公司,在疫情后过度招聘且缺乏营销资金的情况下,正在从计划中的优雅关闭转向利用第三方平台以避免完全崩溃。投资者最初不愿承认失败,但被人工智能驱动的裁员潜力所打动——主要裁减工程、实施和支持岗位。 然而,所选择的平台令人深感担忧。作者将其描述为“氛围编码”——似乎完全通过人工智能提示构建,缺乏人工监督——导致产品充满漏洞、无法使用,并且存在法律违规问题(CCPA、TCPA、ADA)。该平台没有美国客户,并且运营不符合相关法规。 作者负责数据迁移,担心平台的低质量最终会损害客户并进一步取代工人。虽然接受公司的财务困境,但他们难以接受依赖于疏忽构建的软件,认为这代表了一种由易于获得的AI工具所助长的危险趋势。尽管有这些担忧,他们仍然致力于专业地完成过渡。

## 氛围编码SaaS与团队裁员 - 摘要 一篇最近的Hacker News帖子详细描述了一种令人沮丧的经历,一个开发团队实际上被“氛围编码”的SaaS产品取代了。作者哀叹他们的1000人组织在领导层选择快速生成的低质量软件解决方案后,被大幅裁减至约10名员工。 正如评论中讨论的那样,核心问题似乎是缺乏适当的审查以及将削减成本置于质量之上。许多评论者认为原文含糊不清,缺乏关于所涉SaaS的具体信息。然而,一个共同的主题浮出水面:优先考虑速度和低成本(通常由AI辅助编码实现)而非健全的工程实践和经验丰富的开发人员的危险。 讨论强调了人们对日益增多的劣质软件、领导者做出不明智决定的可能性以及对技术专业人员的影响的担忧。虽然一些人认为在适当的保障措施下,AI辅助开发具有潜力,但许多人担心会陷入一场恶性竞争,由于其价格,而“劣质软件”变得可以接受。作者还暗示了这种情况可能产生的潜在法律后果。
相关文章

原文
- 7 min read - Text Only

I considered it a possibility. Now it's set in stone. Instead of fully shutting down in the coming year due to tumbling revenue, leadership decided "What if we use someone else's platform?" It just so happens, the platform they chose is vibe coded.

A vibe coded SaaS killed my team

Like many tech companies during the pandemic, we over-hired and had to contract over and over again. Without the VC-funded war chest that our competitors had, we couldn't compete in marketing and sales. Our brand-awareness shrunk into obscurity.

So, in all fairness, we lost the capitalism game. And, I'm fine with that.

If you're curious, I'm sorry to disappoint. I haven't name-dropped, nor will I now or in the future.

We had a plan to gracefully wind down, unlike Redbox (archived). Once the balance hit a certain threshold, a plan (prepared a year in advance) would have made everyone whole and return the remaining funds to the investors.

Except, the investors changed their mind and would rather take a chance on a future sale than admit defeat.

What's changed their mind?

The allure and promise of AI workforce reduction.

The technology costs are but a single digit percentage of the monthly spend – the majority is tied to headcount and benefits. When I saw the numbers going towards headcount costs, I fully understood the situation we were in.

The previous reduction truly cut headcount to the bare minimum that can still keep the technology we have operating. Any fewer, and there's a high risk of business interruption within a few months.

At the same time, the current revenue projection calls for the end of the business within a few more months.

We used to have a thousand people. Today, I can count everyone on my hands. A cut beyond this will fundamentally need a different operating model.

Given that our revenue can no longer support the staff needed to run our own technology, how do the finances work on someone else's platform?

Assuming that this Software as a Service (SaaS) can deliver what leadership believes, the napkin math suggests it'll work out.

With this SaaS, they expect...

  • No engineering headcount
  • No implementation headcount
  • No support headcount
  • Contracted sales teams to pick up the rest

So if they're going to lay everyone off and migrate to a SaaS, who's going to do the migration?

me

I'll be on my own for an extra month or two to migrate it all over.

Somehow, I need to keep the tech coasting in its last days while migrating all the data that I can.

An warning message saying this version of node (14) will no longer be supported after 2024. It is near the end of 2025.

Thankfully, AWS is not a source of stress for me. Stuff still works, even if it complains years later.

I've expected either a winding down or a transition for over a year now. I've come to terms with an ending like this already.

While my peers are bitter about having a closer end date than me, I'm not as emotionally invested into when or how it ends.

What I didn't expect is how a vibe coded app passed as legitimate to the board of directors. We don't even have a contract with this platform yet and people are told they're being laid off.

ych-some-of-yall-is-why-shampoo-has-instructions

In my two hours of testing and feedback, I found that — without immediate changes to the SaaS — we'd be immediately in violation of the California Consumer Privacy Act (CCPA), California Privacy Rights Act (CPRA), Telephone Consumer Protection Act (TCPA), CAN-SPAM Act, Americans with Disabilities Act (ADA).

I keep saying 'we'. It won't be soon.

How could a platform be that bad? This SaaS has no customers in the United States. Their team is based in another country without similar laws or regulations.

Even so, I'm confident that vibe coded platforms made by people in the United States also unknowingly violate state and federal laws around privacy, communications, and accessibility.

One of our tech acquisitions was through a bankruptcy fire sale after the original company could not make penalty payments for violating the Telephone Consumer Protection Act. These issues cannot be ignored to do business in the United States.

Things don't work

I've used LLM assisted auto complete. I've generated inline functionality. I've generated classes and modules. And I've generated entire web apps. I've seen what GPT, Claude, Z.ai GLM, Grok Code, and Gemeni do across the entire spectrum of software development.

Everyone has a different definition of "vibe coding", and as Theo described the spectrum of its definitions (at 4:30), I'll be using the slice of the spectrum "Ignoring the code entirely and only prompting" as my definition of vibe coding.

Within a minute, I could tell it was made with Claude or GLM. Every picture zooms in on hover for no reason. There are cards everywhere. Links go to # in the footer. Modals have an closing X button that doesn't work. The search button up top doesn't do anything...

It's like someone took some screenshots of a competitor, asked an LLM agent to create design documents around all of them, and then implement those design documents without any human review.

At the shallowest depth, I can see how a CEO got bamboozled. The happiest path is implemented. The second happiest path is rough. The third happiest path is unhinged.

No hacks. No reading the source code. Just innocent clicking around allowed me to break a critical invariant to running a business: I could place orders without giving my contact details or payment.

Besides displacing jobs, issues like this concern me deeply.

LLM-generated code can enable a business process quicker and cheaper than hiring a full team with benefits. With the experts that still value their craft steering the development, software can be produced just as well as without these tools. Business processes meaningfully affect people's lives, whether staff, customer, vendor, or share-holder.

At its extreme with vibe coding, LLM-generated code will have such poor quality that it is negligent to use LLM-generated code without expert oversight and verification. More lives are going to be affected by negligent software than ever before.

It is so much easier to accept that my life is changing because my employer couldn't stay fit in the economy than to accept it being displaced because of broken software made by a machine. The fiscal performance of my employer in this economy is the root cause, of course. And I accept that. Having to pivot everything to some broken SaaS that breaks the law? That's harder to accept.

While it is hard to accept, I'll still do my part and will move on after a job well done. How well the new platform operates after the domain swap is not my problem.

联系我们 contact @ memedata.com