I've previously talked about bootcamps in the general sense. That doesn't exactly provide a great point of reference to how a specific bootcamp fares. So this post will be exactly that and talk to my experience at Hack Reactor. 3 Things I Liked about Hack Reactor
As a former bootcamp instructor and a former bootcamp student, I believe I have a unique perspective to this question. A quick summary. Only attend a bootcamp if: 1. You've done your due diligence on the bootcamp and know that they are selective about who they accept. 2.
What do you learn when you pursue something? There's obviously the skill itself at face value. As a musician, you learn to play music. As a programmer you learn to code. As a writer, you learn to write. There are intricacies within each subdomain that apply to the
When choosing a coding bootcamp, one of the first places you might look is the published outcome statistics. However, while some stats make for nice marketing, they don't tell the whole story. Here's an example: Each program typically publishes a "graduation rate" to indicate
Are all coding bootcamps created equally? Nope. Some coding bootcamps promise to take you from 0 to 100. From newbie-to-job-ready. I went to HackReactor which is more of a 20 to 100 bootcamp that takes intermediate level students to job ready. I would advise against programs that accept total beginners.
I was a newbie developer in 2015 with little to no coding experience and took on the challenge of trying to make it into industry as a software engineer. I'm happy to report that I'm now at Google as a software engineer but it wasn'
The truth about hiring in the industry is that recruiters will often need to filter based on qualifications due to the sheer volume of applicants, not due to a pervasive bias in one way for bootcamp grads or CS grads. So it ends up having a similar effect as systemic