>In ten weeks they will touch on both front and back end and give the attendee the illusion that they are "fullstack devs". This is great because you have a nic

>In ten weeks they will touch on both front and back end and give the attendee the illusion that they are "fullstack devs". This is great because you have a nice shinny Quara clone to show off at the end but in reality most people will walk away with little understanding of either. I think this is a modern problem that not only happens with bootcamps. There's little time to cover both sides in enough depth, IMO. It's better if they focus on one of them, as you suggest. And then there's the problem of the "full-stack" word. I can implement you a full web application by myself, but I wouldn't call myself a "full stack dev" because to be a real full-stack dev, I would then need to have quite a bit of experience on server clustering, load balancing strategies, paralellization of CPU intensive processes, database query and schema optimization, etc...