It doesn't seem like one could learn effectively while fighting physical and mental exhaustion.
Asking people to work 100 hours a week sounds more like an indoctrination program to make them believe that the long work hours they're likely to find in startups are "normal". Or maybe a way for the bootcamp to market their grads to startups: "Our graduates survived 100-hour weeks, so if you're looking for people who are willing to put up with abuse, we have lots of those right here."
These are of course completely different animals, but the scale of learning is similar. Getting a solid intuition for not only web applications but programming fundamentals when starting with neither requires serious effort and is a challenge of breadth. 3 months worth of 40 hour weeks will probably not cut it.
No you're not. I went to Dev Bootcamp. You're required to be present 40 hours a week, any additional hours are because you choose to do so.
"So I'm going to be sitting in class for 40 hours a week?"
"No. That would be terribly boring and ineffective. You will spend a little time every day learning through curated tutorials and books, and a lot of the time practicing what you learn. You'll work in pairs and small groups on an exciting integrated curriculum. Your brain will be buzzing as you solve problems, tackle challenges, and build applications until you're confident in your mastery of the skills. If you have an idea for a web app you want to build, then definitely bring it. Also it's important to note that even though class is 40 hours per week, you'll be working more like 70-100 hours per week!"
P.S.- I also attended Dev Bootcamp (with feministy, as it happens). I'd say 70-100 hours per week was accurate for my cohort, although this varies significantly depending on a student's programming background.
This, I'm sure you'll agree, makes much more sense than simply learning another Algol-based language. To turn this on its head, I can write C & C++ passably but that doesn't mean I'd feel qualified applying for a job as an embedded systems or game developer.
The good thing about DBC is its intensity. We're asked to work upwards of 100 hours a week.* I'm dubious as to exactly where that number comes from and how accurate it is, however it is clear that students work long hours and almost always stay late. I'm told at least a few drop out each term. At least to me, this indicates that the students who complete the program are motivated.
I think the problem is when applicants rely entirely on a three month program to get work. I'm attending DBC not so I can put it on my CV and hop straight into a startup job, but because I genuinely want to add Ruby to my toolbox.
IMO bootcamps shouldn't be taken just to have another line on a resume. They should be a stepping stone, giving the student the tools to contribute to real projects that will give them real experience. I think these contributions that the bootcamp experience allows are where the real value comes from. I apologize if I've been rambling, my point is that bootcamps work best as a part of a bigger and longer story that shows a dedication to the craft of programming.
*Someone mentioned this isn't the case. I'll see if I can dig up where I read this.