Confessions of a $20K bootcamp graduate
medium.com
medium.com
I've been out for almost a year now. I hope they're still keeping the standards high.
That is a very substantial amount of cash for most people. Not to mention the time commitment. (As you say, life is short.)
Easily paid the loan off once I got my first job. Got a huge tax return last month. Now enjoying writing this from Mountain View.
Plenty of people do online programs nearly equivalent to full-time (with loads like that of the 1.5-year track for the OSU second bachelor's, which is also available on 2-, 3-, and 4-year tracks with lower impacts, though longer terms) with full-time jobs and families, some even do full-time programs (like the 1-year track) that way. People that need to learn around an existing job and often family commitments are pretty much the core market for distance education.
That's not to say bootcamps don't have their place, but the idea that there is no other option for people who want to become programmers and can't afford to take a lot of time off of their existing job is just wrong.
At least one program whose graduates I have worked with sets up a payment program that only starts after you land a tech job.
I figured the remote option was really as great as it gets - the majority of the learning still being applicable (many teams work via repositories rather than shared drives anyways) while getting to do the whole thing with no pants from my room in Arizona (much cheaper living expenses).
Having worked at a bootcamp as an instructor and having hired multiple bootcamp grads I've noticed that typically you'll have 2 or 3 really great students and then 20 who got little value from the program. Bootcamps work wonders for that small percentage of students though. A lot of people who had some pretty shitty career paths ended up going from $12.00/hr to $100,00/yr within a few years of the program.
That's life changing; sadly it's the exception, not the rule.
Happens to every super successful small business owner that doesn't consciously try to prevent that from happening. So it's no surprise that HR and probably lots of other bootcamps aren't as great as they used to be.
Bootcamps are a good idea in theory, but the execution makes it clear most of them are cash grabs and part of a disturbing culture in this country to massively profit off post secondary school education (at the expense of the students).
Assuming you're going for a job, paying $X to get a job in six weeks sounds like much better value than paying $X to get a job in two years.
I also think thaumasiotes is missing my overarching point, which is that the data science bootcamps didn't actually provide much value to their students.
However the lack of transparency with bootcamps is frightening. Especially regarding how much they charge. I'm not saying all of them are bad. In fact I think it is refreshing to that so many bootcamps popped up since now you have a lot of options. However there doesn't seem to be a lot of price warring yet which I find kind of odd.
I don't recommend them.
If you truly don't know how to program but want a coding job, then here's a $0 class. Start with JavaScript. Why? The entire internet is based on JavaScript, it can do anything, it runs on any OS, and it's easy to learn.
Google how to write a "hello world" web server program in node.js. (js stands for JavaScript. node.js is the most popular way to write web server in JavaScript). Follow that tutorial through.
Next, update it to make it tell the current time, updating once per second. Make a client-side and a server-side version of the app. Client-side means your code is in the HTML page and gets executed by the browser. Server-side means the code is on the web server, and your browser pings the server once per second for the correct time. Server-side is a bit more complex. Google is your friend in this. stackoverflow.com is a great community and resource to learn from (but search for existing answers before asking questions!).
Next step is to find a TodoMVC tutorial (google again) in node.js, follow it through, and publish to heroku. You probably want to google "node.js todomvc heroku tutorial". (I didn't but I'm sure something would turn up). This will teach you about databases, version control (specifically "git"), hosting, and deployment. At the end of the day you'll have fully functional web app that anyone can use just by knowing the URL! Really once you've worked through that, or, once you're able to do it from scratch without googling much, you're a coder. Rejoice.
At that point put your TodoMVC code on github (google again, but the place people share code via "the git"), and start mucking with it. Whatever suits your fancy: if you're into UX then spend time making the UX cleaner. If you're into databases or programming languages, adapt to different ones. If you're into performance, then blaze that path. Or if you're just not into todo lists, then use your newfound knowledge to start a project WRT something you do like.
Final step, ping potential employers and show off your github account. You'll certainly get a look from SMB owners who are looking for people with some intrinsic motivation. You'll put people who subcontract their drive to bootcamp programs to shame.
I know several people who had a CS degree and/or had been working as actual "Software Engineer"s for fairly reputable companies before attending a bootcamp. For people like this, there are several reasons to attend:
1) The same kind of reason why people do MBA's: you get a mental break, in that you do something very different than what you're used to doing, and then probably get to work in a more desirable city/company.
2) To learn things that were not taught in a CS program. At least as of 3-4 years ago, most CS programs did not teach you any kind of web development-- if you're lucky, there was a class on the LAMP stack, or you could do an independent project using whatever stack you wanted. Otherwise it was Java/C++ for data structures & algorithms. Going from that, to webapp development, can leave you feeling like you have no idea what you're doing. Especially if your coworkers aren't nice enough to help you out.
3) To meet technical cofounders. It sounds like nowadays some programs are basically letting in anyone with a heartbeat, but a few years ago at least, before bootcamps became "cool" or whatever, they attracted highly motivated risk-takers, many of whom had prior programming experience.
One minor nitpick, it wouldn't be Sun née Oracle. The right side is the maiden or former name.
That's unfair. Don't tar everyone with vendor qualifications with the same brush. Many of us obtained them because the companies we worked for needed minimum numbers of vendor "qualified" staff to attain or maintain the various levels of partner status available. For example, I worked at a consultancy that needed to maintain a pool of Microsoft and Cisco qualified staff to maintain the levels of official vendor partnership (Gold was the top MS partnership back in the day, don't remember what the Cisco one was) that would keep opening doors at blue chips.
Conversely, even if you have credentials you're useless if you can't churn out decent code, and it's just not possible to get the chops to do that in a few weeks of study if you don't already have a basic level of skill. And if you do, there's again no reason to actually go to a bootcamp.
Not that we don't have our problems with stuff like brogrammer culture (particularly in startups) but in terms of credentialling we're actually remarkably meritocratic. Pumping out good code is what matters, not the credential. A credential is one signal that an individual may be competent, but just like any other signal it's by no means foolproof, and there's plenty of other ways to demonstrate competence.
If you're going to any bootcamp/immersive and you're going for the curriculum all you're going to get out of it is the curriculum - which you could easily obtain from freecodecamp.com for... well... free. If you're going to go, you should be going for the people - your sprint partners, thesis groups, beer buddies, outcomes teams, tech leads, alumni network... that's what lasts after Hack Reactor and it yields dividends well beyond the (admittedly striking) sticker price.
What "next wave" of server application development does Node.js leave me so woefully unprepared to deal with? Are people really having issues marshalling JSON/XML or sending templates down the wire?
> Another observation, most people who get in, are already qualified people, with top university degrees.
I'm afraid to ask how large their student loans could be, this bootcamp included.
$20k seems like an incredible bargain, but my view is probably warped.
Perhaps the west coast is cheaper? $50,000 per year seems like lunacy to me.
Taking this to the next level, I don't think people should be paying to go to any sort of coding school. Spend the money on a second monitor and living expenses and sit at home and work on building something real. There is no better, quicker or more effective way to learn, and every bit of knowledge that you need is published on the Internet for free.
Stop learning, start doing.
If the only context in which a person is capable of operating is one in which they are "taught" then they aren't suited to programming.
You have to do it on your own eventually so many as well get started on the task of becoming good at that.
I'm a self-taught developer. I learned to program the way that you did, it sounds like, by being curious and tinkering my way through, solving more and more complex problems.
But guess what: that's not how many programmers learned, including some great ones. They went to a structured program and learned there. Where do you get this idea that real programmers are self-taught, so any structured learning is a waste?
Every single online comment thread about coding bootcamps that I've read has had comments from people with your perspective, so you're not alone. But they've also all had people who had no experience programming, went to a bootcamp, and now have good jobs that they enjoy. I know multiple people like that myself...do you think they're all lying? Or maybe you think they must not be REAL programmers?
Programming isn't magical. It's a skill, and just because we taught ourselves doesn't mean everyone has to.
In my case, the outcomes have been good (graduated earlier this year and make $20k more than my previous job) but I would agree that it's been an uphill battle getting an interview and negotiating salaries when there are more junior developers in the market. (HR/MKS markets grads as being more as "mid level" which is accurate for some - but it really is a spectrum.)
Overall I recommend these programs to people who are passionate about the field - but a lot might be motivated to attend for the wrong reasons.
It's always a bummer when an alum would not recommend the program. I hate reading posts like this and I'd love to buy the poster a beer and learn more so we can do it different next time. (Email is in profile!)
Here's a bit of inside baseball:
This post is representative of a troubled period at our school. We had a couple of overlapping key problems and recent alums have been less supportive of the school. We care and we've made big moves to fix it. 1) Candidates were gaming the admissions process -> we rewrote it. 2) Students only had access to 2014 data and didn't know how it was calculated -> we published our 2015 data (and some stuff on 2016) and we published the world's first guide to "how to publish employment statistics that aren't bullshit", and we ramped up messaging to students "expect that your job search might be harder".[A] 3) Students stopped knowing who we were and stopped feeling like they could trust us -> we bought back two leaders to focus full-time on the campus (vs working at the umbrella organization). Lots of smaller changes as well.
Even during this difficult period, students are generally having a great experience and getting an ROI that we are proud of. Our most recent NPS measurements have all been above 80, which is bonkers. (This means that nearly everyone is a 9 or a 10 on a 1-10 scale of "how likely are you to recommend HR to a friend?")
There are a lot of details in this post that I don't disagree with. Eg "Ironically the number of lectures drops dramatically after the first week." This is true and we tell students about it during w1. It's the correct design decision. Etc. For other students, those same details have added up to a different gestalt. We care and we try to fix things when things aren't adding up. The diagnosis is not linear (you can't just fix the problems that alums cite) but we listen and try to sort out the right decisions.
I empathize with a lot of things going on and I want recent alums to know we care. I also think it's bonkers that our 98% placement rate in 2015 (94% in 3 months, ~85%ish in 3 months for one recent cohort) is being cited like it's weak sauce. That's a towering accomplishment of staggering magnitude in my books, and we charge $20k because the median student gets a ~$50k raise and we employ lots of staff to make that happen.
<3, Shawn
[A] http://www.hackreactor.com/student-outcomes, http://reactorcore.com/wp-content/uploads/2016/05/StandardSt...
Horseshit alert if I've ever heard one.
Sounds legit.
I, too, got a six-figure "raise" from middle school to today.
You got into google because google actively recruits military vets, not because of the bootcamp experience, which might have helped get you over the hump, but unlikely caused it.
It took you 3 years between shift lead and google.
~your lovely neighborhood ex-people search engine founder.
P.S. thank you for your navy service (in all seriousness)
As far as the 3 years since Walgreens goes... - 1 year spent in college for CS before dropping out - 1 year spent self-teaching and working for a startup where I learned what "jQuery" and "AJAX" and "PHP" did =p - 3 months Hack Reactor - 6 months contract with Intel - currently at Google
If not this would have got to that number after maybe 2 years so definitely helped.
Like, where are all of the grads employed by Hack Reactor to pad the numbers accounted for? What percentage of your students already have a CS degree when they walk in the door? Why is the size of the average class increasing at the same time the price is going up? Most importantly, why do some big name companies effectively blacklist your graduates now, and what are you doing about it?
Your "towering accomplishment of staggering magnitude" looks like marketing hype and a lack of transparency.
On grads employed by HR: they are not counted as successful job seekers. Again, you can read about this in the methodology.
On big name companies blacklisting our grads: I have literally never heard of this. Google was our # 2 employer in 2015.
[1] http://reactorcore.com/wp-content/uploads/2016/05/StandardSt...
Also, I believe there is only a single company that has 'blacklisted' HR grads, and it was because they had a bad interpersonal experience with a few people from a single cohort.
Would love to hear a more thorough explanation of this.
I actually liked the problems but it seems like there weren't enough different kinds of questions to filter out people with the answers beforehand.
If you use the same test for months the fact is the answers will leak. People that take it again will do well the second time, regardless of whether they are qualified. This is a failure on your part, not on the applicants part. You need to own up to this and not blame applicants for gaming the admissions process.
It is understandable that we didn't know who you were and couldn't trust you. I have never seen you in my life. I saw Marcus one time in the first week. Talking about how you are going to change things for the future is fine, but it doesn't help those who went through the "troubled period".
It just leaves me with a bad taste in my mouth when things go south that you rush to blame people "gaming the admissions process" and not we screwed up, we are fixing it for the future, and here is how we are helping those affected.
Even the author said they got a job after a couple months! Which is exactly what the school promised. How does the poster feel like they wasted their time/money??
Also, the author has no grounds to say HR isn't the best, cause they haven't been to others. I can't say it's the best either. I can say I had an excellent experience, and so did all of my class, and many others. And I do have 3 friends off the top of my head who have gone to other bootcamps, and they all cited those as having major problems (no help finding jobs, bad teachers). Anyway, this post sounds whiny. HR does excellent work.
Nothing against node.js, but a candidate would be marketable to a broader range of shops if the program gave them a basic grounding in Python and SQL. Python is well accepted for both web servers and sysadmin type scripting. SQL is the most common choice for databases. I don't think either one would be a incremental burden and would really open up the number of potential employers for the grads.
Don't get me wrong, Python is great and has a number of really great number crunching libraries just a pip away, but if all you're doing is developing web apps and hashing out some scripts via the terminal... they'll need to know JavaScript for the client - but do they really need to come away with two languages after 3 months?
Seems like people fail to realize that the language is the medium through which they teach concepts (algorithms, data structures, etc).
I'm an HR06 grad; we focused on fullstack Javascript, but that hasn't stopped me from working in Ruby/Rails, or more recently, Go.
Beyond that, we did actually have lectures/sprints on MySql, Postgresql and Mongodb. Not sure if that's changed at all.
Do Udacity nanodegrees fall under the same category as these bootcamps? What is the quality one can expect there?
Shawn responds with some details about recent changes we had to make to address, among other things, applicants figuring out how to game our admissions. For a few cycles there were notably more students than usual who struggled with the program, not getting out of it what other students do and who subsequently struggled in the job search. That placed a huge demand on instructional resources which has impact throughout the student body.
Whether those students got in by deliberate exploitation of vulnerabilities in our process (some did) or earnestly researching what HR wants and studying "to the exam" is immaterial -- they entered unprepared for the program. Regardless, they received the same world-class curriculum as our phenomenally successful students. I don't believe it's coincidental that the most vindictive account of a student's experience at Hack Reactor came hot on the heels of that challenging period in our history.
I do want to address a few assertions that were made that suggest a deliberate attempt to mislead readers. The Hackers In Residence are not Instructors at Hack Reactor. They aren't represented as such. HIR's are not intended to be experts in technology nor to provide answers to all possible questions the current students provide. Any instruction they provide is either ad-hoc coaching, whiteboarding collaboration, in the form of brown bag talks they offer or by presenting toy problem solutions in the morning.
What they are is a group of very gifted and empathetic engineers who are sharing their talents with other students, coaching them through problem solving, providing first line Help Desk support, pitching in on other efforts at the school while they continue their own studies beyond the scope of our curriculum. They are among our brightest students who choose not to go immediately into the job market where they can command impressive salaries but rather stay to learn and study more and to support other students. They're fabulous, talented people.
More specifically, HIR's are recent grads who understand the experience of the current students and who know from direct recent experience the kinds of support they found most helpful or most hoped for and seek to provide that support to students. Questions that are beyond the scope of their understanding are escalated to engineers (like me) on the Instruction Team. They are an additional set of eyes and ears that allow me to even more insight into the experience of my current students than I can gain on my own.
As to the lectures and the difference between the first half and the second half of the program. The curriculum is very specifically designed to develop autonomous engineers. It is WHY our grads are successful. They don't excel in the workplace IN SPITE OF that structure. We guide them more early in the program where they need more support and very consciously, over time, reduce the hand-holding in favor of their own discovery and collaborating with classmates to learn. Mentors and Lecturers continue to provide support and instruction as needed during the latter half of the program.
With respect to languages. Many schools teach more than one language. Not many schools prepare engineers as well as we do. Hack Reactor is not a Javascript school. We use Javascript as a context to teach software engineering. Our students often tackle new languages on their own in the second half because they are well-prepared and appropriately autonomous. We've had students and student teams use Swift, Python, Ruby on Rails, Rust, Processing, dabble in IoT, ... And HIRs tackle Scala, Haskell, and more. That's not in spite of the program, that's because of the program..
I understand that a critical reader will have to take my response with a grain of salt but I think it's reasonable to ask readers of the Medium article to do their own research and contact alums for direct feedback before drawing conclusions.
You give yourself so much benefit of the doubt, but offer none to the author, who you've decided is out to get Hack Reactor? That one swipe at the former student is more concerning than the rest of your comment is reassuring, to me.
An alternative reading of the situation, if you're not seeing one: the author has attempted to better herself by one common approach in the programming world, and having a bad experience, she is sending a warning back to others who are seeking the same improvement, telling us, 'this may be the wrong direction.'
Seems reasonable to me.