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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Ask HN: When to Use a Dev Shop?

1 点作者 michaelmarkell超过 4 年前
At a startup, sometimes the core team lacks bandwidth for certain projects. In these cases, hiring an outside dev shop seems like an interesting option. Of course, there are some trade-offs, in terms of maintenance, knowledge transfer, quality, risk, timelines, etc.<p>For all those seasoned devs&#x2F;eng leaders out there, what are your heuristics for when it is a right, or wrong, call?

1 comment

blizkreeg超过 4 年前
I&#x27;m an experienced dev&#x2F;fmr eng leader and (disclaimer) run a small product dev shop now.<p>In the past, I&#x27;ve hired a dev shop&#x2F;freelancer when the project could be worked on fairly independently with high level direction and has a strong business use case but it isn&#x27;t worth wasting core team cycles. For eg, marketing team needs a dashboard, the reporting&#x2F;ETL infra needs to setup or is broken, internal products, or even clearing the bug backlog. Ideally the dev shop also has someone who can do some product&#x2F;design work if necessary.<p>If you&#x27;re hiring a dev shop for higher velocity&#x2F;shipping features quicker, you have to be careful. Reviewing their PRs, communication (if in different TZs), sharing context, poorly done work, and disconnect between team&#x27;s best practices and theirs can eat into your core team&#x27;s time and potentially lead to some frustration.<p>As much as possible, the key is to protect your team&#x27;s time aside from critical inflection points -- initial scope, them sharing their approach, validating if it looks good, and the occasional review&#x2F;check-in.<p>Hope this helps.