My experience has been that, no matter how smart and awesome the new guy is, it's not reasonable to expect a several day learning curve. In general (insert many caveats here), I expect that the new guy will be fully ramped up in about 3 months. If it's more than that, there's probably a problem (or the thing is just REALLY hard!). If it's less than that, I get nervous and I await future problems, because we almost certainly skipped something!
I'd agree that for any development, there's 2 points of lag
the new guy doesn't do things as fast as the old guy, until he's been there a while
the old guy isn't working at 100% efficieny because he's teaching the new guy.
In a big team this fits into the wash of people being people - people come, people go, people are always learning new things - so they are fast one week, and slow the next.
But in a small team (sounds like it's you plus the other guy), this can be rough.
It's worth negotiating with your manager and pointing out that 2 people will not immediately be able to do twice your current workload. Chances are that the first month, you'll manage about 75%-85% of your workload, while the new guy will manage the work at maybe 50% of your speed. After the first assignment gets done, chances are that you'll be able to get closer to your regular pace, while the new guy will need 2-3 more assignments to reach full throttle.
I think this really depends on the skillset of the guy you're supposed to mentor. If he's an experienced dev who has a history of learning new technologies then I guess it's doable. Otherwise it's going to be tough.
NB: I don't have experience in exactly the same situation so take this with a grain of salt.
This is a common management problem. Having a knowledge transfer plus a little mentoring will not result in someone who is 100% up to speed.
You should try to come up with a "ramp up" time frame so that you can more accurately estimate when the new developer can contribute roughly as much as you do to the project.
Personally, I think it is ridiculous to put this type of time scale on something like this. As @Jakub says, "this really depends on the skillset of the guy you're suppose to mentor." I've been in similar positions where I have 1 week to get someone up to speed on something I've spent the last 2 1/2 years learning, researching, and developing. I picked the most important aspects and did the best I could.
All in all, there are too many uncontrolled variables in my opinion. Just prioritize and make it clear that the guy you are mentoring has some serious studying ahead of him.
Limited experience of technologies involved and no knowledge of the CMS... I find it extremely unlikely (read: impossible) that he'll be able to produce production-quality code in 10 days. Not only that, but this will also slow you down.
Realistically I'd try to lower management's expectations as much as possible as soon as possible. Privately, I'd fantasize about beating someone up with a rolled-up copy of The Mythical Man-Month.
It is hard to generalize because some developers need a lot more mentoring then others.
On one project, I spent a month mentoring a new developer, with me holding his hand, he accomplished slightly more in a month, than an equally inexperienced developer did in a couple of days.
It also dependents a great deal on the project. A well structured and documented project should be much easier for an experienced programmer to dive into.
Sometimes 2 weeks is all that's needed for a new guy to start being productive. Without knowing what the requirements of the new guys work is it is impossible to tell.
For example, the work might be just making some css changes to your existing CMS. In that case, 10 days is overkill as you should be able to explain the relevant styles in short order.
Another example would be making minor changes to a specific module. Let's say you they just need to add a field. Again, 10 days, even training a very new guy should be more than enough.
Point is: the scope of their immediate requirements will define whether the time involved is good enough.
btw, another factor is your own work speed. Don't take this the wrong way, but the new guy could pick up things in a couple hours that you spent weeks learning. We're all different with different backgrounds and capabilities. Of course, by the same token, the new guy might spend weeks on a piece that you figured out in an hour. ;)
发布评论
评论（7）
我的经验是，无论新人多么聪明和出色，期望几天的学习曲线是不合理的。一般来说（在此插入许多注意事项），我预计新人将在大约 3 个月内完全提升。如果不止于此，则可能存在问题（或者事情真的很难！）。如果少于这个值，我会感到紧张并等待未来的问题，因为我们几乎肯定会跳过一些东西！
我同意，对于任何开发，都会有 2 个点的滞后，
在一个大团队中，这符合人的本质——人们来，人们走，人们总是在学习新事物——所以他们一周快，下一周慢。
但在一个小团队中（听起来像是你加上另一个人），这可能会很困难。
值得与您的经理协商并指出两个人无法立即完成当前工作量的两倍。很可能第一个月，你将管理大约 75%-85% 的工作量，而新人将以你的 50% 的速度管理工作。第一个任务完成后，您很可能能够接近正常节奏，而新人则需要再完成 2-3 个任务才能达到全速前进。
My experience has been that, no matter how smart and awesome the new guy is, it's not reasonable to expect a several day learning curve. In general (insert many caveats here), I expect that the new guy will be fully ramped up in about 3 months. If it's more than that, there's probably a problem (or the thing is just REALLY hard!). If it's less than that, I get nervous and I await future problems, because we almost certainly skipped something!
I'd agree that for any development, there's 2 points of lag
In a big team this fits into the wash of people being people - people come, people go, people are always learning new things - so they are fast one week, and slow the next.
But in a small team (sounds like it's you plus the other guy), this can be rough.
It's worth negotiating with your manager and pointing out that 2 people will not immediately be able to do twice your current workload. Chances are that the first month, you'll manage about 75%-85% of your workload, while the new guy will manage the work at maybe 50% of your speed. After the first assignment gets done, chances are that you'll be able to get closer to your regular pace, while the new guy will need 2-3 more assignments to reach full throttle.
我认为这实际上取决于你要指导的人的技能。如果他是一位经验丰富的开发人员，有学习新技术的历史，那么我想这是可行的。不然会很艰难。
注意：我没有完全相同情况的经验，所以对此持保留态度。
I think this really depends on the skillset of the guy you're supposed to mentor. If he's an experienced dev who has a history of learning new technologies then I guess it's doable. Otherwise it's going to be tough.
NB: I don't have experience in exactly the same situation so take this with a grain of salt.
这是一个常见的管理问题。知识转移加上一点指导不会让某人 100% 跟上进度。
您应该尝试制定一个“提升”时间框架，以便您可以更准确地估计新开发人员何时可以为项目做出大致与您一样多的贡献。
This is a common management problem. Having a knowledge transfer plus a little mentoring will not result in someone who is 100% up to speed.
You should try to come up with a "ramp up" time frame so that you can more accurately estimate when the new developer can contribute roughly as much as you do to the project.
就我个人而言，我认为将这种类型的时间尺度放在这样的事情上是荒谬的。正如@Jakub 所说，“这实际上取决于你要指导的人的技能。”我也曾担任过类似的职位，我有 1 周的时间让别人加快了解我在过去 2 1/2 年里学习、研究和开发的东西。我选择了最重要的方面并尽我所能。
总而言之，我认为不可控的变量太多了。只需优先考虑并明确表示您所指导的人需要认真学习。
Personally, I think it is ridiculous to put this type of time scale on something like this. As @Jakub says, "this really depends on the skillset of the guy you're suppose to mentor." I've been in similar positions where I have 1 week to get someone up to speed on something I've spent the last 2 1/2 years learning, researching, and developing. I picked the most important aspects and did the best I could.
All in all, there are too many uncontrolled variables in my opinion. Just prioritize and make it clear that the guy you are mentoring has some serious studying ahead of him.
所涉及的技术经验有限，并且对 CMS 缺乏了解……我发现他极不可能（读作：不可能）在 10 天内生成生产质量的代码。不仅如此，这还会减慢你的速度。
实际上，我会尽快尝试尽可能降低管理层的期望。私下里，我幻想着用一本《人月神话》的卷轴殴打某人。
Limited experience of technologies involved and no knowledge of the CMS... I find it extremely unlikely (read: impossible) that he'll be able to produce production-quality code in 10 days. Not only that, but this will also slow you down.
Realistically I'd try to lower management's expectations as much as possible as soon as possible. Privately, I'd fantasize about beating someone up with a rolled-up copy of The Mythical Man-Month.
这很难一概而论，因为有些开发人员比其他开发人员需要更多的指导。
在一个项目中，我花了一个月的时间指导一位新开发人员，我握着他的手，他在一个月内完成的工作比一个同样缺乏经验的开发人员在几天内完成的工作要多一些。
它还在很大程度上取决于项目。对于经验丰富的程序员来说，结构良好且记录良好的项目应该更容易深入研究。
It is hard to generalize because some developers need a lot more mentoring then others.
On one project, I spent a month mentoring a new developer, with me holding his hand, he accomplished slightly more in a month, than an equally inexperienced developer did in a couple of days.
It also dependents a great deal on the project. A well structured and documented project should be much easier for an experienced programmer to dive into.
有时，新人只需要 2 周时间就可以开始高效工作。如果不知道新人的工作要求是什么，就无法判断。
例如，工作可能只是对现有 CMS 进行一些 CSS 更改。在这种情况下，10 天就太过分了，因为您应该能够在短时间内解释相关样式。
另一个例子是对特定模块进行微小的更改。假设您只需要添加一个字段。再说一次，10天，即使训练一个非常新的人也应该足够了。
要点是：他们当前需求的范围将决定所涉及的时间是否足够。
顺便说一句，另一个因素是你自己的工作速度。不要误解这一点，但是新人可以在几个小时内学会你花了几周时间学习的东西。我们都有不同的背景和能力。当然，出于同样的原因，新人可能会花几周的时间来完成你在一个小时内就想出来的作品。 ;)
Sometimes 2 weeks is all that's needed for a new guy to start being productive. Without knowing what the requirements of the new guys work is it is impossible to tell.
For example, the work might be just making some css changes to your existing CMS. In that case, 10 days is overkill as you should be able to explain the relevant styles in short order.
Another example would be making minor changes to a specific module. Let's say you they just need to add a field. Again, 10 days, even training a very new guy should be more than enough.
Point is: the scope of their immediate requirements will define whether the time involved is good enough.
btw, another factor is your own work speed. Don't take this the wrong way, but the new guy could pick up things in a couple hours that you spent weeks learning. We're all different with different backgrounds and capabilities. Of course, by the same token, the new guy might spend weeks on a piece that you figured out in an hour. ;)