3 ms·
Hiring directly is a lot of work, especially in domains that you don't have expertise. The article cited workers helping to train Bard- this task is nothing lik
by scottyah 3y ago
Hiring directly is a lot of work, especially in domains that you don't have expertise. The article cited workers helping to train Bard- this task is nothing like hiring Software Engineers, you know it won't last forever, and it will never be a strategic core competency to build up at your company.
So, you sub out the work to another company that has more focus on sourcing employees and keeping enough hired/productive so you can focus on developing the algorithms instead of those managerial tasks. This model is extremely common in all industries that aren't 100% vertically integrated. The only difference is that in the physical world it's easier to point to products being sold than in this knowledge work where the deliverables aren't as concrete.
In the end, these moves by a small group of people just ends up ruining the perks for the rest of the contractors. The current argument of "We work in the same office, drink the same coffee, eat the same food, and work on the same projects" has one very obvious remedy, which is to take away those perks.
- FireBeyond 3y ago> Hiring directly is a lot of work, especially in domains that you don't have expertise Seriously? "Google had the expertise to design and develop Bard, but they lacked the expertise to train Bard, so they had to go to outside contracters"?