If you also assume that people strengthen their own understanding of a topic if they teach it new engineers don't drain resources if they ask other developers questions. They might make your other workers more productive in the long run. At the very least I'd argue that the time other devs spend on onboarding isn't wasted 100%.
I suppose the dynamics change if you hire fairly bad people who make things worse with their early commits but that mostly means your hiring process (and most likely your code review or whatever measure you set up to prevent bad code) is broken.
In practice I've found this assumption is only true if you have very small growth/turnover. I.e. If you hire a new engineer once every couple of years it's probably the case, but if you hire a new engineer every few months it isn't.
On average I'd say we have our senior engineers spend 40-50 hours total in the first month teaching/helping a new senior dev. Probably a similar number of hours in the second month, and then it drops to maybe 10 hours/month for the next year.
From what I have seen a new senior dev is around 10% of the productivity of a existing senior dev for the first month, 20% for the second, and rapidly reaching 80% by the end of a year.
So they are at 1 unit/hour of productivity for the first month and add 160 units of productivity for the month. However, senior devs, at a cost of 10 units/hr, have spent 40-50 hours helping them at a cost of 400-500 units of productivity.
Second month they add 320 units but cost another 400-500. By the third month they add maybe 450 units and only cost 100 units. And at this point they have managed to pretty much break even.
Of course if you assume training costs are not a real cost but rather beneficial for your existing senior devs then the new senior dev looks productive from the first month. But then you are really just talking past each other.
Meanwhile some of my friends at large companies "train" for weeks. Pretty interesting difference.
A programmer should be able to checkout, build, run in minutes and then to start fixing bugs on day 1.
I have never met a programmer who could do that. I'm sure some of them can, in specific domains. But I'd consider expecting that to be a huge red flag: I've worked at exactly one place that expected a day 1 hire to match their veteran coders, and I wouldn't work there again.
i.e. If it takes someone 3 months to be productive, there's probably something wrong with the build system/documentation, or code organisation/structure (+ comments, or lack of), lots of knowledge in people's heads etc.
My main objection was that there shouldn't be 3 months of negative or near zero productivity. Or there should at least be a good reason for it.
Welcome to the midsized, pre IPO startup.
That ramp up period involves learning the subtleties of the business, inter-team dynamics and processes.
The first bug I ever fixed resulted in costs for the company. My mentor had left the company within a week of me starting and I waded into the code with good intentions, but put us out of compliance with regulations.
You wouldn't let them check out and run the code? The business processes etc all have to be learned of course, but the code is where most of the time should be spent.
> The first bug I ever fixed resulted in costs for the company. My mentor had left the company within a week of me starting and I waded into the code with good intentions, but put us out of compliance with regulations.
I would consider that a failure of the company, too many responsibilities are pushed down to the developer. If there are strict compliance regulations then there should have been some sort of QA process and/or a domain expert validating the results.
This is detached room reality. There arent many jobs (other than junior level programmer) where you just churn out code without actually having to think about the requirements, use cases, security, etc. Having responsibilities is a very common thing as a software engineer.
But expecting the developers to act as the domain experts is also detached from reality. I've never worked with anyone who I would consider a domain expert that also keeps up to date on a technical level.