The other is that ya, coaching and training is hard. There's a post somewhere else in thread about some guy hating his job cause he needs to coach up new bootcamp hires for like a year or something to get fully up to speed.
Let's not lie to ourselves about how long "eventually" (in eventually get good) is. I just took a quick look at my province's college of trades, and they quote 6000 hours (5280 hours on work and 720 hours in school) of apprenticeship/training before being considered "competent" at welding. If you go look at a bunch of the more technical "blue collar" jobs or trades (like mechanical draftsman, HVAC technician, etc), you all see numbers around that mark. Now, there's surely some fudgery going on. Very likely by the last year of their apprenticeships, you'll have many apprentices that are infact ready to just be done and are just logging hours for the book... but still, I think its a relevant guide. Even at half the length, you're talking roughly a year to a year and a half (which matches up well with other poster's experience coincidentally...) to train up.
Seems like the bootcamps might be a good subsitute for the "in class" portion of these apprenticeship programs, but nothing more.
But clearly there is demand for a lot more programmers than NBA players. The kind of people who make good programmers are competing with people going into law and finance. More programmers means less lawyers and less business people. Which I guess is fine, but it is weird to just assume anyone can do it.
It's the IBM of the 2010's.