4 ms·
I'm a cofounder at Hack Reactor, and I also attended this meeting. (Sup Gregorio!) Here's my 2c on the 3 things he says we could not agree on: 1. "All progra
by shawndrost 10y ago
I'm a cofounder at Hack Reactor, and I also attended this meeting. (Sup Gregorio!) Here's my 2c on the 3 things he says we could not agree on:
1. "All programs must report their graduation rate and what constitutes a graduate (not only their completion rate)." I can't remember this being a topic, so I feel like I must have missed something.
2. "All programs must report how many graduates are employed as full-time software developers, and separate other tech-related jobs, and non-full-time forms of employment from this metric." Gregorio is right about this: bootcamps should be transparent about this. Reasonable people can disagree about whether a bootcamp should count eg "growth hackers" in employment figures (Hack Reactor would not, per our methodology[1]) BUT bootcamps should DEFINITELY make that data available. This was shot down.
3. "All programs must make available the raw data that they used to base their metrics." Again, I can't remember when we talked about this. It's kind of a good idea, but unless you have robust non-employment data, an anonymized data dump is a csv with like 3 columns. Ours just had salaries, outcome codes, and time-to-hire (which we already published in histogram form), so we didn't bother publishing it. (Turing's has lots of fun demographic data that would be out-of-scope for an industry standard about employment.)
- shoemai 10y agoDo you find that every student wants to be a full time developer though? What if the student were fully capable of finding a job as a developer but that's not what they wanted to do? Or maybe they were just open to many possibilities. Seems like just have a simple statistic like % of students that became devs would be 1. misleading and 2. acting against the bootcamp's own interests.