Earlier quoted context omitted.
Ditto! I went to a bootcamp after having worked in aerospace for 6+ years and, I had a mechanical engineering degree. I had programmed for a long time and had no problem with basic algorithm exercises (of the kind they spend the early part of these camps on). [1] The problem is, there was no easy way -- for someone like me wanting to go into software -- to (convincingly) say, "Hey, I can code and think abstractly. Gi…
> Frustratingly, the instructors were very unhelpful at the stuff I needed help with the most -- forming a mental model of how and why Rails works. I suspect that's because they didn't know how or why. Rails has a lot of magic -- just follow the convention and it works. Magic can be good, because it encourages a standard. Unfortunately, many Rails programmers seem comfortable leaving the magic as a mystery rather tha…
Bootcamps vs. College
311–320 of 449 posts
Re: Bootcamps vs. College
#312Earlier quoted context omitted.
> when I was a new grad I started on the codebase more or less right away I did as well, but... > Didn't even have code reviews back then. Not so much this one. > If you have to train them, then it seems the coding part should be cheaper then the algo part. I do actually agree. But there tends to be other aspects of the job outside of just code and algorithms. Prior work experience is a shining star compared to a 22…
I don't know, we pay people to do a job. Sure some coworkers become friends, but most don't. As long as people are somewhat easy to get along with I don't think we should focus too much on other stuff.
Re: Bootcamps vs. College
#313There are several factors that don't enter this analysis. 1. Bootcamps can be selective over a range of non-academic criteria such as interview skills, personal hygene, and prior work experience. Or to put it another way, unlike a public university, a boot camp can select for culture fit both in its internal cohorts and in the workplaces it targets. 2. Bootcamps tend to attract people with previous work experience: s…
Isn't not letting C students graduate a good thing?
My reaction was, "Well we would likely reduce the rate at which security vulnerabilities are introduced in new code."
Then I reread it. :-)
(And I criticize C with love. I used it for years and recognize it as a product of its original purpose.)
Re: Bootcamps vs. College
#314Earlier quoted context omitted.
> The only thing most grads have on bootcamp people is algorithm knowledge. "Just teach algorithms." Do you have two years to spare to do so? Because I'm a platform engineer and I regularly use the extent of my CS mathematics education to write better code--you'd think this'd just be Ruby slinging, "what sort of math do you need to automate systems", but it ends up being remarkably more than that! But you know what e…
I like your post and agree with most of what you said, except about the algorithms. I don't think you need 2 years to teach them. You need a highschool level understanding of Math and about a week. Obviously this varies from person to person - but I learned them extremely quickly. I think where we are not seeing eye to eye here is that I envision a bootcamper that has a high aptitude for abstract thought, can read qu…
Re: Bootcamps vs. College
#315I swear, articles like this are going to cause me to have an existential crisis. I started learning programming as a child in the 80s. More than 30 years later, I like to think that I've acquired a lot of valuable knowledge and experience across a broad range of topics, and yet... when I hear about people training for three months and walking into decent jobs, I start to wonder what actually differentiates me at all.…
And that matters. A big part of what you've learned in 30 years is mistakes not to make. It's the bugs you don't write, and the bad architectures you don't build. That makes you a much better programmer, even if you know less about the new shiny than someone who just went through a bootcamp.
Re: Bootcamps vs. College
#316Earlier quoted context omitted.
> Frustratingly, the instructors were very unhelpful at the stuff I needed help with the most -- forming a mental model of how and why Rails works. I suspect that's because they didn't know how or why. Rails has a lot of magic -- just follow the convention and it works. Magic can be good, because it encourages a standard. Unfortunately, many Rails programmers seem comfortable leaving the magic as a mystery rather tha…
Magic is great, until it stops working and you have to figure out why.
Re: Bootcamps vs. College
#317Earlier quoted context omitted.
Isn't not letting C students graduate a good thing?
When I first read your comment I thought you meant the language C. My reaction was, "Well we would likely reduce the rate at which security vulnerabilities are introduced in new code." Then I reread it. :-) (And I criticize C with love. I used it for years and recognize it as a product of its original purpose.)
Re: Bootcamps vs. College
#318At launch, there was a lot of pent up demand. 400 people applied for a Ruby class of 25. Most that took that first class had been self taught and in the surveys said they had been hacking at projects for an average of 18 months. Code school was a way to speed their path into a professional developer role (note developer, not engineer).
The majority of students today already have a degree and are looking to switch careers, average age of ~30. They are looking for skills to transition so in that way, going back to college isn't an option unless it's for advanced degree. The same is true for the veterans that are transitioning to the workforce, they have been in a very structured environment and want to speed through job ready training vs. four more years at college.
"Stack switchers" tend to be the top of the compensation range. If you have 10 years of .Net experience and want to switch to iOS. You'll earn top dollar. If you don't have much real world experience you'll land an entry level JavaScript job with that skill.
The needs of hiring companies has also shifted as the market has matured. There are more "code school grads" in the market looking for jobs, so the process of screening needs to be better, interviews need to be improved and tools like triplebyte.com improve transparency of skills. Hiring Junior developers has never been the preference for employers. Everyone would rather hire both skill and experience. But when you're competing with larger companies in a hot job market, you'll often take Junior talent that is a good culture fit.
By culture fit I mean a combination of past education, work experience and new skills. Combine that with work ethic and desire and you see why most of the strong code schools have a high (90%+) placement rate.
Curriculum have changed as well. Code schools have to be teaching at the front end of the hiring demand. Teaching an old tech stack where job postings are heading down won't work. Review StackOverflows recent survey if you're curious about stack preferences.
Code schools are also required to be licensed with each state where they do business. That's a requirement not all schools follow. It's really about consumer protection in that way so check with your state.
The industry is still immature and you're correct that there isn't any reporting standards, e.g. are placements rates reported at 90 or 180 days past graduation, etc? We're working with a number of companies like the Iron Yard to standardize on reporting and moving to audited results over time. I hope that someday we can apply the same placement rate standards to other academic institutions. As a dad of college age kids that would be amazing (note the White House tried that two years ago with a scorecard and the Universities said no).
Regarding the debate of should everyone learn to code or no one learn to code? It's a skill, it's not for everyone. It's a job that isn't for everyone. There are a lot of online resources, information sessions and one day courses, start with the low risk version and see if it's for you. With an average starting salary of $71k in Seattle, the compensation appeal is a strong draw for people outside of the tech industry. You may be drawn to the compensation just make sure that you are also drawn to the work.
Re: Bootcamps vs. College
#319I swear, articles like this are going to cause me to have an existential crisis. I started learning programming as a child in the 80s. More than 30 years later, I like to think that I've acquired a lot of valuable knowledge and experience across a broad range of topics, and yet... when I hear about people training for three months and walking into decent jobs, I start to wonder what actually differentiates me at all.…
I jumped through a few of these hoops early on but since I have a breadth of experience instead of a laser specific focus on one technology, I'm apparently getting disqualified from some of these positions. It's been a really weird experience for me. I mostly gave up, figuring that if I lost my current (good) job I'd have the free time to devote 16+ hours each week interviewing/applying for the types of gigs I want. Our industry is bizarre at times.
It's weird being on the other end. Almost all of my jobs have come from word of mouth and personal networking where I never even needed to interview. I interview and hire all of my engineers by taking them to lunch and just getting a feel for their interests and personality, so seeing how everyone else seems to be doing it has been a huge culture shock.
Re: Bootcamps vs. College
#320Earlier quoted context omitted.
My CS degree was four years of heavy abstract thinking. If you can get those skills elsewhere great, but I don't think it's that common.
Based on what? The amount of bias in this thread is very strange. I think what's going on is that the people with CS degrees invested a significant chunk of their life and a significant amount of money into getting a CS degree. Therefore they're invested in denying the possibility that the qualities they achieved through their program can be achieved without. The article presents some evidence in support of this poss…
Is it? Their sample is only people who can pass their initial screening.
> We do background-blind screening via an online programming test, and only interview engineers who pass this test. Thus we have no way to know what percentage of bootcamp grads and college grads fail early in our process, and the graph above reflects only people who pass our test.
Even ignoring that,
> worse at algorithms and understanding how computers work
would support the point.