3 ms·

If your point is one must understand 100% of computing before being hired as a software engineer none of us would ever be hired. You can produce value long bef

If your point is one must understand 100% of computing before being hired as a software engineer none of us would ever be hired. You can produce value long before you understand everything there is to know, of course, and a lot of being a software engineer is being able to problem solve on the job. BloomTech exists to help people get to the point they can do that and create value. No school can pretend to teach everything there possibly could be to know about how software works.

user3939382 4y ago
My point isn’t to learn 100% but how about 5 or 10? The complexity of the work just doesn’t seem to match the duration of these programs.
- austenallred 4y ago
  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. That's kind of beautiful, actually.
  - user3939382 4y ago
    > 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.
    - austenallred 4y ago
      850 actual hours, butt-in-seat and required, or 850 scheduled hours?
      - user3939382 4y ago
        The rules are complex but feds require 90% attendance for clock hour programs receiving financial aid.
- nemo44x 4y ago
  A lot of software jobs are collecting data from a source, doing something with that data, and then putting it somewhere. It’s just CRUD over and over.

user3939382 4y ago

My point isn’t to learn 100% but how about 5 or 10? The complexity of the work just doesn’t seem to match the duration of these programs.

austenallred 4y ago
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. That's kind of beautiful, actually.
- user3939382 4y ago
  > 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.
  - austenallred 4y ago
    850 actual hours, butt-in-seat and required, or 850 scheduled hours?
    - user3939382 4y ago
      The rules are complex but feds require 90% attendance for clock hour programs receiving financial aid.
nemo44x 4y ago
A lot of software jobs are collecting data from a source, doing something with that data, and then putting it somewhere. It’s just CRUD over and over.