We made a conscious decision to try and hire someone from these camps as an experiment. I went to their demo day and winnowed the graduating class of 40 down to 6. Of the 6 we interviewed we decided to give 6 month internships to 3 of them, 2 developer and 1 qa. Despite being hourly with minimal benefits, they were making the yearly equivalent of 50k a year which I found more than reasonable given the fact they had n…
> He was a smart guy, but he needed years more experience to operate at the level of our other engineers and he was demanding a 75k salary.
Two questions: Are you in San Francisco, and which bootcamp was this?
We made a conscious decision to try and hire someone from these camps as an experiment. I went to their demo day and winnowed the graduating class of 40 down to 6. Of the 6 we interviewed we decided to give 6 month internships to 3 of them, 2 developer and 1 qa. Despite being hourly with minimal benefits, they were making the yearly equivalent of 50k a year which I found more than reasonable given the fact they had n…
What area are you in? 75k in NY or SF for an inexperienced developer seems high.
Millions more lines of instantly legacy code written by inexperienced programmers? Thank the gods we'll all be employed for decades! Decades I tell you! ;p
My reaction was more along the lines of "I'd hate to be the person who has to clean all that up)."
Mine was more along the lines of, "I'm going to make so much money cleaning that shit up."
We live in a computer age. Knowing how to program is no longer a "specialized skill", it's mandatory (on some level) to effectively interact with ever more complex systems that run our lives.
Somehow I have a hard time believing that if you have a math major, the only difference between you waiting tables and living on the brink of poverty or making bank as a software engineer is a 3 months Ruby course (I have a double math/CS major); I feel like there may be something more going on here. I'm happy for the gentleman's success, but it seems like a poor example to use in any case.
Shouldn't a math degree already have at least a little programming? Matlab? Python? Something?
Should? Maybe. But plenty of math graduates have little to no programming experience, even from top schools.
We made a conscious decision to try and hire someone from these camps as an experiment. I went to their demo day and winnowed the graduating class of 40 down to 6. Of the 6 we interviewed we decided to give 6 month internships to 3 of them, 2 developer and 1 qa. Despite being hourly with minimal benefits, they were making the yearly equivalent of 50k a year which I found more than reasonable given the fact they had n…
> He was a smart guy, but he needed years more experience to operate at the level of our other engineers and he was demanding a 75k salary. Two questions: Are you in San Francisco, and which bootcamp was this?
Yeah these are vitally important questions. The curriculums and the level rigor of the different bootcamps varies widely.
Some have a very high bar for entry and are basically just a way for someone who could quickly become competent (i.e. someone with a deep math or some type of engineering background) to ramp up on coding.
Others just let anyone in and teach very basic things so the graduates level would vary widely as well.
While the demand is real, I am just not sure it will last with the level of skills being pumped out of these bootcamps. I recently interviewed a few candidates from a coding bootcamp mentioned in the article and while they can write basic rails code, they all lacked problem solving skills. Most candidates were hung up on basic performance related questions.
Even "experienced" developers who haven't had formal computer science training can run into performance problems. At my last job, our application was running slower and slower as we added clients. None of the Ruby devs could figure it out, the code was "fine", all of the tests passed and ran quickly (with a stubbed 10 item customer table), and everything ran great until we grew beyond a hundred or so customers so it…
I've seen this happen with experienced developer with a CS degree. They say, it's "not my job" to test with large data. B.S., it is your job so sit down, shut up and do it. The job of QA isn't to find all your bugs, it's to ensure you don't have any.
Millions more lines of instantly legacy code written by inexperienced programmers? Thank the gods we'll all be employed for decades! Decades I tell you! ;p
As long as these rookies aren't writing nuclear reactor firmware, who cares? Most of programming is mundane. Have them make CRUD apps while we experts work on something interesting ;)
> Have the[se rookies] make CRUD apps while we experts work on something interesting
The reality is the opposite: the smooth-talking aptitudeless "rookies" with a years experience 7 times get themselves onto teams designing "interesting" stuff from scratch, then the programming experts are put on the team to clean up the many bugs for years to come.
Millions more lines of instantly legacy code written by inexperienced programmers? Thank the gods we'll all be employed for decades! Decades I tell you! ;p
As long as these rookies aren't writing nuclear reactor firmware, who cares? Most of programming is mundane. Have them make CRUD apps while we experts work on something interesting ;)
> Have them make CRUD apps while we experts work on something interesting