TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: Should you ship an MVP if your team isn't agile

3 点作者 JulianMiller520超过 13 年前
I've been working with a vendor who is clearly on to something product-wise but the version they shipped is buggy and simple things like modal window controls aren't working. They impressed in the beginning but now the bosses are talking about ditching them because they aren't able to fix the features they shipped in a timely manner. It really made me wonder if they've done damage by shipping too early. Thoughts?

1 comment

lucisferre超过 13 年前
What I'm guessing you are looking at is a prototype, whether they know it or not, and it is rarely a good idea to simply try to fix the bugs in a prototype. They are great for validating early assumptions but typically should be thrown away once that cycle is completed and rewritten.<p>Trying to improve and fix prototype code is typically very challenging. It often has no architecture or structure, so changes and new features are slow to implement.<p>If this vendor doesn't understand this, or it seems likely that having them rewrite it would just result in another prototype quality result then your bosses are right to walk away.
评论 #3286966 未加载