开发速度并不是瓶颈

[

](https://substackcdn.com/image/fetch/$s_!ha53!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8cb306df-4a8b-4ec6-bf86-8b87073a29a7_3473x1951.jpeg)

"You are wrong, Pawel. You can vibe code a successful product without any technical skills. Here's one example."
“你错了，Pawel。即便没有任何技术能力，你也可以用 vibe coding 打造一款成功的产品。这里就有一个例子。”

I liked the challenge, especially since it referenced a source. What I thought would be a short comment evolved into a series of articles.

我喜欢这个挑战，尤其是因为它引用了来源。我原本以为是条简短评论，结果演变成一系列文章。

This post is the last one (or at least I believe so at the time of writing), and I will focus on the product management side. Well, just one aspect of it.

这是本系列的最后一篇（至少在我写下这句话时，我是这么认为的），我将聚焦于产品管理这一侧。嗯，其实只是其中的一个方面。

The perception that the pace of shipping features (or building in general) is the bottleneck of product development is a misconception.

认为“功能发布（或整体构建）的速度是产品开发的瓶颈”这一看法，其实是一种误解。

Ultimately, that's what vibe coding tools offer: we can build it for you with no engineering team whatsoever. In fact, the original challenge was worded along the same lines:

归根结底，vibe coding 工具提供的正是这一点：无需任何工程团队，我们就能为你构建产品。事实上，最初的挑战也正是这样表述的：

"I'm working with people and I've seen others, who only used AI to create a valid tech business, scaling it up beyond a million dollars, before they hired any software engineer."
“我正在与一些人合作，也见过其他人，他们只用 AI 就打造出一个可行的科技业务，并在还没雇佣任何软件工程师之前就把它扩展到百万美元以上。”

Let’s unpack it, then.

那就来拆解一下。

I'm a fan of vibe coding when it comes to prototyping. It is a fabulous tool to learn whether what we ideate is desirable. The first thing about prototypes, though? They are disposable**.**

在原型阶段，我是 vibe coding 的拥趸。它是验证我们想法是否值得追求的绝佳工具。但关于原型，首要原则是什么？它们可丢弃。

Even if we validate that we were right and our idea works (which happens maybe once every ten at...