Bootcamps have failed one after another. The most well known, Lambda, is even desperate enough they will "loan" you a new "grad" for free to try to get you to hire one . And that's not even scratching the surface of what's wrong with bootcamps in general, like having instructors barely a few months ahead of students giving out lectures and grading assignments .
I can't say I've seen anyone out of a bootcamp that was a great hire. I guess these online coding schools might cater to motivated teenagers that are interesting in trying out CS before enrolling in a proper degree. But there's no money to be made there.
My own experience has been that there's no correlation between where the dev graduated from and how productive/valuable/etc they've been at work. I've seen just as many rock-star bootcamp grads as I have complete wastes of space from Stanford/CMU/MIT.
There could be some filtering function here like the pool of grads who made a significant effort to come to the US afterwards, but yeah. 100% rockstars every time.
Don't just take my word for it -- from the lips of pg himself:
Waterloo internships last 3.5 months. 16-18 weeks. That's ~150-200% longer than some other schools summer internships.
Computer science students graduate with roughly 2 full years of work experience at 6 different orgs. Not including any extra curriculars.
Waterloo load balances internships across the entire year. Each class of CS is split into four schedules. Students will study in the summer and they will do internships in the fall and winter.
Many, many big companies offer internships to Waterloo coops students in the fall and winter. I'm not sure if other students are ever available at these times.
At Waterloo, computer science is a math degree and they teach students how to prove things. It's one of the first things they learn.
Also, we learn lisp as a first course in programming.
> Many, many big companies offer internships to Waterloo coops students in the fall and winter. I'm not sure if other students are ever available at these times.
From my experience hiring, most target schools don't offer every classes at every semester (they are just too small). So taking a fall/winter internship can delay graduation by a whole year.
So I used to get flooded by resumes from Waterloo for the fall and winter because they were the only ones to apply (coupled with the school being larger than my usual target schools combined together!).
Humour me! At Waterloo, nobody gets kicked out of school for not doing co-op. It is an optional program. You must be talking about something else.
> From my experience hiring, most target schools don't offer every classes at every semester (they are just too small). So taking a fall/winter internship can delay graduation by a whole year.
At Waterloo some specialized upper-year courses are only offered once a year, but the first 2 years of courses are usually available year round.
My first internship was Sept - Dec 2013. They liked me enough that they asked me to stay an extra 4 months. I was able to say Yes immediately. I just took all my 2B ("second half of sophomore year") courses in the summer after working until May.
But you'll get kicked out of co-op for not having internships right? I meant someone can't graduate co-op without working in industry.
It's trivial to switch to non-co-op Computer Science. The co-op program admins try to guilt you out of it, but there isn't any real penalty.
The admins want to keep upper year students in the program to attract companies, since companies often want to hire more experienced interns.
Why do students drop co-op in later years? The co-op program costs extra (~$1500/year). There's some more or less useless professional development courses you must take, as well as reports you must write after 5/6 terms. In other words it can be a somewhat expensive hassle.
Maybe the one thing the co-op program can provide is they help with J1 visa to the USA. And tax incentives for Canadian companies to hire interns. Those benefits often aren't enough of a draw for someone who has 1+ years professional experience at 3-4 companies.
Hence, what often happens is that upper year students drop co-op or go outside the program to find internships. They find their own jobs, in some cases the company arranges the J1 for them.
For example this term, a bunch of Waterloo coops wanted to go to SF, but the coop program wasn't offering positions which required travel to the USA due to covid. They just made arrangements with the companies directly.
I have also had extremely positive experiences with Waterloo grads (and student interns), and I kinda wish that I had done a program structured in the same way. In particular, the program requires that students do several "co-op" work terms, so by the time they graduate, they've worked in multiple organizations and have the equivalent of more than a year's work experience. They have a better idea of what kind of work is a good fit for them, they know they can be productive in real projects, and they have some exposure to the organizational/communication/process portion of getting stuff done as well.
We complain sometimes about the disconnect between software engineering and the "computer science" curriculum -- and it turns out that actually having a thoughtfully composed "software engineering" program is a pretty good and natural solution.
I think they Astroturf a lot. At least on this site. Any thread about a class at Stanford/MIT/CMU (often because they posted the textbook for free) and someone from Waterloo will post what they teach, no matter if it's relevant.
It's also a giant school (36,000 undergrads and 6,000 postgrads) and from what alumni told me, undergrads are incentivized to apply everywhere and especially during the off-cycles (winter) for internships when they are effectively the only ones looking.
Contrast that with Stanford that's barely 7,000 undergrads and 10,000 grad students).
I think they also have to get internships to even stay in the program (it's coop) so I guess that weeds out the unemployable.
The coop program is probably their biggest strength. Working with coop interns is fantastic and almost always leads to a job post graduation.
Nearly everyone in my AppAcademy cohort was already a STEM grad and some from top schools. Also that didn't correlate with performance as the person with the most advanced degree was unhirable and the degreeless folks are among the most successful. More than half a decade on, we're still at like 98% of our cohort with long and successful careers. The few cohorts ahead of and behind me have similar results. More than half of my cohort are senior ICs at this point as well (staff engineers, architects, startup CTOs, etc).
Most of us didn't even need the bootcamp, per-se, but were there for the helpful aspects of building a portfolio in a short time and the psychological benefits of being coached through the interview process.
_YOU_ may not have seen successful bootcamp grads, but you also might not be in any of the places where they're looking for work. Or you have a very strong bias.
: Dev Bootcamp, GA, AppAcademy and Flatiron School are/were easily more well-known than Lambda School ever was.
> Most of us didn't even need the bootcamp, per-se
I think you hit the nail on this one. Today kids take https://missing.csail.mit.edu/ instead of doing a bootcamp. "Intro to CS" classes are also more prevalent (and sometimes mandatory) for everyone in STEM nowadays.
I think we all felt that way. Is that worth the high cost of tuition? Debatable. We're just about all working though.
I was changing careers after a decade plus of low-level grunt IT jobs when I was capable of doing so much more. It took probably 3-5 years just to build my confidence enough to do the bootcamp -- I had developer friends who were telling me for years I was more than qualified and capable but I'd found it so hard just to start.
A huge part of the lack of confidence has to do with growing up always being poor. The idea of a stable, high-paying job that's rewarding is almost unimaginable from that position.
Crowded space and the businesses were service oriented (not infinitely scaling like software) so very different success & risk profiles.
For the students... Most were lied to about the outcome statistics, but many people were able to leverage it into new career.
> I can't say I've seen anyone out of a bootcamp that was a great hire.
Most people aren't going to brand themselves as boot camp grads if they don't have to.
They had (at the time), really good teachers, and the forums were a great source of knowledge.
I wonder if their particular niche of online education is tougher nowadays. There seems to be a wealth of online platforms tailored towards the "professional skills" edge of the market—if I ever need a course on migrating to Azure using only a TI-86 calculator while respecting HIPAA, I'm sure Pluralsight has a course—but when I think of the more general "learn to code" style courses, I don't think of Treehouse anymore.
In particular, having watched multiple family members/friends transition into software development (coming from no real background in code) over the last couple years, I've noticed they swing between two extremes:
1. Completely free resources, like FreeCodeCamp, CodeAcademy's free plan, or App Academy Open.
2. Going all-in on an immersive bootcamp, typically with some kind of job placement assistance program at the end.
I wonder if more middle-of-the-road premium options like Treehouse are losing marketshare to this. Though obviously, this is big time anecdata.
I don't agree with the no management change they did but thought the 4 day workweek was a smart idea. Microsoft japan reported that a 4 day workweek increased productivity by 40% - https://www.npr.org/2019/11/04/776163853/microsoft-japan-say...
Do not attribute 32 hour work week to not being successful, it was incredible and allowed for a ton of creative work to come to life.
A. Interactive features (scrimba.com)
B. Mentors (demandcurve.com)
C. Credentials (Udacity, Coursera)
E. Convenient access to frequent updates (blinkist, shortform, getabstract)
There are also non-scalable parts - access to expert, prestige, and all the bits you've mentioned. I think that's probably where the future of ed-tech is going.
Is one that's doing Community/Cohort style learning by pairing Devs, PMs and Designers together to learn.
Back in 2012-2013 it was amazing. I sunk countless hours into the videos and thought it was a great value.
After building some basic sites I decided to take the plunge and enroll in a bootcamp. Fast forward to today and I’m incredibly thankful for taking these steps.
They forgot to include a link to the spreadsheet.
I found it here → https://twitter.com/nickrp/status/1436747911220457482
(and in case they delete the Twitter post) → https://docs.google.com/spreadsheets/d/1D8419ThkbOibfMcGQRUi...
Treehouse are skewed towards beginners but I wonder if the market for beginner content is too saturated? Udemy dominates for paid video courses (for beginners) and YouTube covers the free tutorials option.
Also, Treehouse's content is divided into lots of separate videos. It's a big collection of videos but it isn't always obvious how each video relates to another - I wonder if this confuses beginners? I presume this more modular approach was designed to let learners tailor their own learning path. Or to flexibly arrange the content into modular tracks.
Contrast the Udemy approach: The all-in-one course for a language or topic that promises the user a more linear curriculum. Of course, the quality of Udemy courses can vary hugely, but there's no doubt the all-in-one course is appealing to beginner learners.
These is a small but helpful YouTube channel which reviews online learning platforms (Udemy, Pluralsight, etc) called Tech Course Review. Here is an informative review of Treehouse from December 2020:
Treehouse Review 2021: Is Treehouse worth it?
I always liked Treehouse's presentation but it was a bit pricey compared to other services like Udemy for example.
They were video lessons on HTML, CSS, and other languages. Your comment makes no sense, and sounds more like projection than valid criticism.