5 ms·
Why not hire someone you think is smart but inexperienced into a low level programming job? There's lots of chores that don't exactly take a lot of deep knowle
by maxerickson 8y ago
Why not hire someone you think is smart but inexperienced into a low level programming job?
There's lots of chores that don't exactly take a lot of deep knowledge.
(Of course the answer is that companies have discarded the idea of having a training pipeline)
- alanfranz 8y ago> There's lots of chores that don't exactly take a lot of deep knowledge. I think you're doing it wrong. I don't work this way. If it's a low level job, I'll find a way to automate it. I want all my coworkers to grow to a good level. At my company, we do train newcomers and young people, and we then hope they stay. But it's an investment that doesn't pay off every time. Other companies just hire experienced developers, by paying more than us... but they don't have a training pipeline. And we can't pay more (we're a small company) because we already spend a lot in training... sob.
- mattkrause 8y agoThe frustrating thing is that how comically adverse some places are to training. One place recently passed on me for an R&D position because I had experience with Torque rather than Slurm. I have a PhD and a bunch of research experience—-it would take maybe an afternoon to figure out how to submit jobs on their system...
- alanfranz 8y agoI hope it was an HR screening, not a technical interview.
- marcinzm 8y agoThe problem with training is that you hire 10 people. 3 of them pan out. Then they leave for 100% more salary from a company that doesn't need to make up for hiring those other 7 in the first place. In my experience companies that rely on armies of junior programmers to do things manually tend to end with horrible code bases and a lot of technical debt. Few abstractions, lots of repetition, little automation and so on.
- maxerickson 8y agoHow many people are panning out in the non training scenario?
- codingdave 8y agoIf you have two people in front of you, both equally smart, both equally inexperienced, one straight out of high school, one graduating with a degree, why would you not hire the one with more education and years of analytical thought under their belt? When I got out of college, I took the same low-paying entry level jobs that the 18 year old high school graduates did. I didn't get a jump start because of my degree. But I was able to use the skills I had learned (even in my Fine Arts education), to more deeply approach problems and I moved in my career more quickly. I'm still in touch with some of the folks from that very first job. They are struggling -- they spent decades in tech jobs, advancing, making more money, doing bigger things... but all eventually experienced a layoff, and can't get re-hired despite their skills and experience because younger folk, cheaper folk, with 10 years experience can do everything they can, and demand less salary. Nobody cares that you know 25 year old tech. So the usefulness of a degree isn't about day one of your career. It is about years 3-5, when you have a few years of skills built up, and then can synthesize them into something bigger and better, and start to make bigger jumps on your career, and put yourself in a position that you are more than just your tech knowledge. And that is what employers care about once you get old.
- jandrewrogers 8y agoI think this improperly assumes the possible and even probable level of sophistication of people without a degrees. To reframe the question you initially posed: if you have two inexperienced but otherwise technically indistinguishable people in front of you, which is more impressive? The one that spent four years sitting in classes or the one that did it entirely by self-study? For the rest of your career, almost all of your future ability and value will be the product of ongoing self-study, not what you studied in class.
- maxerickson 8y agoIf you beg the question, you get the framing you want. What if you've got 3 inexperienced candidates in front of you?