I can't speak for other code bootcamps, but BloomTech is at 960+ hours for our shortest program, and considerably longer for our longer ones. And it's really hard, intentionally.
That's an absolute minimum six months full-time (and a lot of students spen dmore than 40 hours/week) with no breaks; longer hour for hour than the time in a CS degree spent on software-related topics (though those vary far more widely than most of us like to pretend).
If you eliminate context switching, have the right tooling and instruction, yeah you aren't coming out the other side a principal engineer, but you can certainly build stuff, contribute to code the right way on teams, understand data structures and algorithms enough to make stuff performant, problem solve and build a whole lot of stuff and a lot of value.
That's enough to start getting paid, and 30 years later you can continue to marvel at how you're still just scratching the surface.
> BloomTech is at 960+ hours for our shortest program
I helped run a large school for 6 years with 4,000 students/year who took an 850 hour program. Sad to say that amount of training isn't necessarily as much as it sounds.
That's an absolute minimum six months full-time (and a lot of students spen dmore than 40 hours/week) with no breaks; longer hour for hour than the time in a CS degree spent on software-related topics (though those vary far more widely than most of us like to pretend).
If you eliminate context switching, have the right tooling and instruction, yeah you aren't coming out the other side a principal engineer, but you can certainly build stuff, contribute to code the right way on teams, understand data structures and algorithms enough to make stuff performant, problem solve and build a whole lot of stuff and a lot of value.
That's enough to start getting paid, and 30 years later you can continue to marvel at how you're still just scratching the surface.
That's kind of beautiful, actually.