3 ms·
I understand there are some difficulties with this ideology in terms of technology companies and onboarding, but I have also seen the potential benefits of such
by bob1029 6y ago
I understand there are some difficulties with this ideology in terms of technology companies and onboarding, but I have also seen the potential benefits of such an approach without explicitly attempting to engage it.
We have hired entry-level engineers that went from supporting basic production issues to writing low-level parts of the platform within 2-3 years. At no point was I consciously aware of any explicit knowledge transfer occurring, but somehow these individuals are able to pick up a tremendous amount of capability via proximity to the day-to-day process. One day it clicked for me that a pull request I was reviewing for one of these individuals was something that I would expect to see from a highly-skilled developer on the team. Seemingly overnight, we converted a QA/Support engineer who chases down basic null refs into a proper developer, and all it required was exposing them to the full depth of the process every day.
Perhaps the master/apprentice game doesn't make sense in terms of on-boarding. But, I see massive amounts of value in exposing willing employees to increasingly-difficult problems on a daily basis. Make your most junior employee install the same tools and work through the same processes that your most senior employees do. There is no reason you cannot ramp someone from zero to hero in a few years with passive exposure to your business processes.
I find that this model of constant exposure combined with probationary employment strategies provides an excellent blended approach for ramping in new talent that would otherwise be filtered out by your typical big corp HR department. Just because someone doesn't have a computer science degree or got burned by our incredibly shitty legal system doesn't mean they aren't willing to bust their ass and try to prove something to the world. I would like to give as many people a chance as possible at this. Programming is an art and no one policy is going to be the best. The more perspectives we have the better.
- loopz 6y agoThis is the natural way, which most people would resent and reject. Screwed up incentives need to be fixed first.
- imtringued 6y agoI don't think it has to be codified, just recognized. Too many people in this submission read into the article and assume that the guild is a gatekeeper whose primary interest is keeping trade secrets. It's the opposite in reality. The entire idea behind a guild is that you give young people with zero skills an opportunity to learn the craft. Right now the American system is the opposite. People have to take care of their own education before they can get the job by going to university. There are jobs where this makes a lot of sense and there are jobs where its just pointless busywork.