6 ms·
>> but as soon as you threw any real world problem that required any deviation from their established lane they completely floundered. Eventually we just starte
by andrewstuart 7y ago
>> but as soon as you threw any real world problem that required any deviation from their established lane they completely floundered. Eventually we just started filtering out anybody with that background.
I don't think this is the measure of people new to coding.
If 40 people have gone to the trouble and effort and cost of doing a bootcamp and not a single one of them is good enough for you then maybe it's you who are wrong.
The correct measure for people new to coding is work ethic/effort and enthusiasm and energy and friendliness and ability to communicate about ordinary non technical things. Pretty much nothing else counts. If someone works really really hard at learning to program then they'll get there eventually.
Tell me who it is that starts to learn to program and can instantly "get real world things done"? It would make no sense if someone was both new to programming and also could "get real world things done".
People develop their ability to get real world things done over time - it means nothing if a newly minted programmer comes out of the gate without an impressive ability to get "real world things done".
Programming starts with fumbling around finding your feet, then struggling with syntax, then after lots of enthusiasm time energy practice and effort people develop the skills to get stuff done.
So sorry I do not agree with your assessment of 40 coding camp graduates being unemployable - you just don't know how to assess brand new programmers.
- azhenley 7y agoYou're making some big assumptions about their interview process. Maybe new CS grads from 4 year programs are passing the interviews (and being successful on the job), in which case their filter may be working well.
- sky_rw 7y agoNone of the graduates I talked to could handle CS grad level questions, especially the typical ones you get at any given tech startup large or small (sorting, binary search, etc), and I never approached my interviews with them that way. Here is a real-world way I would try to asses somebody's capabilities fairly given their experience. Each candidate generally has a capstone project. Some kinda small app like a todo list or something written in Rails. I would have them walk me through the app they built, explaining some things that they did and asking why they made decisions a certain way. This was an incredibly soft test just to make sure THEY actually wrote it, as frequently code would be shared or TA's would help a lot. I wanted to know that they knew why they did something. If that went well, which it often didn't, I would give them a small feature to add. Something like "how would you expand your authentication to have a password reset", then hold their hand while we walked through adding this feature. I'm all for non-traditional educations especially when it comes to SWE, but at the end of the day you are applying to a 6-figure job in a competitive market. The failure here is on the Bootcamps that convinced these people that 3 months of study can qualify your for ANY 6 figure job. Compare this to a traditional vocational school. I get the spirit of the parent comment, trust me I really do. But I can sign up for a 28-week metal fabrication course and be guaranteed that I will learn how to weld and get a $60k/year job as a welder. Startup bootcamps are marketing to the same people, with the same vocational messaging. It just is not the same, and it's bad for everybody.
- ktaylor 7y agoQuestions such as pseudocode a "(sorting, binary search, etc)" algorithm on the whiteboard are BS questions used to haze interviewees and make the interviewer feel like the big man on campus. Almost no working programmer ever implements any of this BS unless they are doing very specialized work. I've interviewed 100s of programmers for several very well known tech company and specifically tried to get tech interviewers to tone that down. Doing so allowed us to hire some great non-CS JR programmers who are now team leads and even CTOs at other companies.
- sky_rw 7y agoI completely agree
- rglullis 7y agoSorry, but if some "brand new programmer" can't get any real work done, then it is not a programmer at all. There can be even excellent students or someone to invest further time and resources, but professionals, they are not.
- andrewstuart 7y ago>> but professionals, they are not This is exactly correct. And if you're interviewing juniors/graduates trying to find "professionals" then you really don't understand hiring. "We're looking for professionals with no commercial experience." It's a contradiction in terms.
- whiddershins 7y agoSo you want to pay someone to train them.
- pmiller2 7y agoWhy not? That's how it used to work. Provided they can demonstrate a minimum of CS fundamentals, things like tools (git, ssh, etc.), how to work with a large code base, good style, and any number of things that a new grad needs to know to become a competent junior engineer can be taught.
- OGWhales 7y agoI think this is exactly what the original comment was taking issue with for the bootcampers. >but as soon as you threw any real world problem that required any deviation from their established lane they completely floundered He quoted it himself, but failed to notice the issue. I myself have noticed people who went through 4 year programs tend to be much more adaptable as the universities tend to do a better job of building a solid foundation.
- rglullis 7y agoBS. For a corporate setting that may have the resources to hire people for the potential and long term maintenance of their cogs, sure, hire "recent graduates" with zero ability to produce any value to the company. But don't tell me that you can't find young people with little to no experience that are talented enough to run circles on any "experienced professional" and actually be useful from the start. I've done it myself more than once.