3 ms·

Huh. I went through devbootcamp 3 years ago and stay in touch with a fair amount of people who did bootcamps. Haven't really heard this one before. The anecdote

Huh. I went through devbootcamp 3 years ago and stay in touch with a fair amount of people who did bootcamps. Haven't really heard this one before. The anecdotes I've heard are actually the opposite direction; that the bootcamp grads hit the ground running because they know the framework and general toolset for web dev (plus are usually spending a huge amount of time outside of work leveling up) and the CS majors take longer to be productive. Of course, as their careers go beyond "junior", the bootcamps grads need to do major lifting to catch up in other areas beyond basic web dev. But early on, I've only really heard good things. Curious.

shados 9y ago
People from good universities do co-ops, internships, and side work. They know the frameworks already too. And then you have some who don't, but come from MIT or CMU and pick that stuff up faster than I can link to the tutorial (well, once they're done complaining its not Haskell anyway, lol) Though it does remind me of a company I worked for that hired a lot of bootcamp peeps, and it was hailed as a giant success by management. Meanwhile the rest of the team was grumbling about having to do 2x the work as they had to pick up the slack. (Now, obviously, I do know some people who went through bootcamps that do amazing. I also know some 100% self taught engineers who are now Principal engineers or similar at Google or Microsoft. The above is just what I've seen to be the common case). Teaching React or how to build an API controller to someone we just hired is never the bottleneck. Interns pick that up just fine, no matter where they come from.
- austenallred 9y ago
  I think the majority of it is sheer time. A bootcamp grad has generally been coding for three months. A CS grad has (ideally) been programming for four years. Take a bootcamp grad after 3.5 years of work vs a fresh CS grad and it's (often) a no-brainer, up until you start running into the need for theoretical knowledge a CS grad has. I've never once heard a bootcamp talk about scaling or architecture in any real way.

shados 9y ago

People from good universities do co-ops, internships, and side work. They know the frameworks already too. And then you have some who don't, but come from MIT or CMU and pick that stuff up faster than I can link to the tutorial (well, once they're done complaining its not Haskell anyway, lol) Though it does remind me of a company I worked for that hired a lot of bootcamp peeps, and it was hailed as a giant success by management. Meanwhile the rest of the team was grumbling about having to do 2x the work as they had to pick up the slack. (Now, obviously, I do know some people who went through bootcamps that do amazing. I also know some 100% self taught engineers who are now Principal engineers or similar at Google or Microsoft. The above is just what I've seen to be the common case). Teaching React or how to build an API controller to someone we just hired is never the bottleneck. Interns pick that up just fine, no matter where they come from.

austenallred 9y ago
I think the majority of it is sheer time. A bootcamp grad has generally been coding for three months. A CS grad has (ideally) been programming for four years. Take a bootcamp grad after 3.5 years of work vs a fresh CS grad and it's (often) a no-brainer, up until you start running into the need for theoretical knowledge a CS grad has. I've never once heard a bootcamp talk about scaling or architecture in any real way.