5 ms·
Hummmm... you wonder how much of that money is invested in internal training for those skills they claim they cannot find. I bet the average is pretty close to
by austincheney 10y ago
Hummmm... you wonder how much of that money is invested in internal training for those skills they claim they cannot find. I bet the average is pretty close to 0. I guess it just makes more sense to throw money at the problem and hope for magic in 43 days.
Instead, why not just devote that $33K to a training program for a duration of roughly 43 days? Now you have the skills you were missing with the bonus of added loyalty and lower risk at no additional cost (money and time that would have been spent anyways). You also get a massive productivity boost for free according to Brook's Law. The only cost is that an external candidate might (or might not) have a diversity of skills your company doesn't provide.
- shams93 10y agoTraining never happens at least not in the us and not even in big companies the big companies here have largely sent the work overseas and when it is local they use temps
- tomwinter 10y ago+1
- struppi 10y agoTraining is also a good idea since bringing a new person to a team has a negative effect on the productivity of the team (#): (1) If you are not working on a greenfield project, it takes some time for the new hire to get up to speed. During that time, their productivity is negative: They are not really productive yet, and they need help from everyone else on the team. (2) If you add people to a mature team (or remove people), the team dynamics change completely and the team might need several months to get back to their previous performance again (##). So, hiring a new developer can cost you several tens of thousands of dollars / euros even after you already hired them. Training your existing developers can make sense here - They get a productivity boost sooner. And, when I teach inhouse-trainings, I always have a feeling that people are more motivated to do their job after the training, even when they cannot immediately use what they have learned: It matters to them that their employer cares about them and their technical excellence. Still it often makes sense: Some times, you just don't have enough people for your long term plans. But don't expect too much too early. (#) Adding people to a late software project makes it later / You cannot get a baby in one month by hiring a team of nine women. (##) I collected some data about this when I was an agile coach for two teams at a large company. We added 2 developers, productivity dropped, needed ~6 months to become reliably higher than before adding the developers. Unfortunately, I cannot share the data. Also, I guess this was an extreme case: Complicated legacy system.
- OpenDrapery 10y agoSounds like we've found the guy who has the secret to measuring productivity. Care to share what the rest of the industry has yet to figure out? How, on earth, do we measure developer productivity?
- citizens 10y agoLook at the commits?
- struppi 10y agoI know that this every productivity measurement is very fuzzy and can be cheated (#), but here's how we did it: We were simply looking at the number of features delivered to the customer in a certain amount of time, number of defects found in production and number of critical defects found immediately after roll-out (a.k.a. hot-fixes). We adjusted for holidays, vacations and sick leaves. Those numbers were relatively stable until we changed the team, then dropped, and it took quite a while to reliably get to higher levels than before. (#) I don't think the team cheated, because if they had, they could have easily cheated the numbers in a way that they'd steadily rise.
- flukus 10y ago> Those numbers were relatively stable until we changed the team, then dropped, and it took quite a while to reliably get to higher levels than before. That could be a reflection on a number of things, most notably the code quality. If your new hires are taking a while to get up to speed (you didn't specify how long) then that's also an indication of either quality or doing something quite different.
- projektfu 10y agoBy definition, you cannot train a Senior Developer in 43 days, as that takes years. But it would be interesting to find out how much companies can save on recruiting by hiring promising entry-level developers rather than chasing rarer and more expensive Senior Developers. On the other hand, what is the potential loss from putting developers in over their head? As always, the most important figures that one needs for management are unknown and unknowable (Lloyd S. Nelson).