Hey Shawn, Jesse, here. For those just tuning in, Shawn & I know each other and I help run Dev Bootcamp. Tony Phillips, one of Shawn's co-founders, was a tea

Hey Shawn, Jesse, here. For those just tuning in, Shawn & I know each other and I help run Dev Bootcamp. Tony Phillips, one of Shawn's co-founders, was a teacher-in-training at Dev Bootcamp for 5 months and before that a student in our first, 8-week cohort. A few corrections: 1. Our current cohort has 54 students. Starting January 28th, we'll have 48 students in the space at a given time. Although it's been challenging, we've so far been able to increase group cohesion as we increase class size. Below a certain size it's very easy for students to feel isolated if they can't find at least one other student to identify with. 2. Although our core hours are 9AM-6PM Monday-Friday, most students are here 12+ hours per day, 6-7 days per week. 75% of the class was here last weekend, for example. We keep a tight container on core hours and give students flexibility on off hours. The average student is working for about ~750 hours over the course of Dev Bootcamp. Also, about 50% of each cohort comes from out-of-state, and about 20% have families and children. Trust me, they're "tak[ing] time off [their] normal life." 3. We've worked with around ~100 companies over the course of our hiring days and none of them are asking for a longer training period. If an employer is skeptical, there's little difference between 9, 10, or 12 weeks. Twitter hired one of our summer students as an intern, for example, and their initial skepticism was more along the lines of, "How could 10 weeks compare to a 4-year University CS education?" That's a rough paraphrase from a conversation I had with a head of their head of college recruiting in April. On the flip side, virtually all employers return for future hiring days and about half send employees to become mentors for students in the following DBC class. I'll grant you that we might be talking to different employers.