I'm not sure that's true, other than the obvious issue of supply vs. demand, where wages are concerned. As for quality, I've worked with college-trained programmers who wrote awful code, and I've worked with self-taught programmers who wrote amazing code. Some of the best programmers I've ever worked with were self-taught.
I never attended a bootcamp, but I have mentored for Rails Girls, Girl Develop It, and a bootcamp or two. In my experience, bootcamps are good places to learn how to write certain types of code. They don't help much in the way of theory, algorithms, or other low-level details, but for teaching people how to write typical business applications, they are a pretty good place to start, I think.
I also think bootcamps are good at weeding out those with no aptitude or desire for programming. My wife attended a bootcamp, and there were two types of people who attended with her. Those who took the task seriously, studied the materials, read the books, and practiced, practiced, practiced, and those who thought that paying the $5,000 to $10,000 was all the effort they had to apply, and that someone else would magically load their minds with the requisite information, once they had achieved that monetary apex. The first types got jobs. The latter types did not.
In my experience, a lot of it came down to how people approached the program. It was either:
"I have n weeks to learn as much as I can in order to catch up and be competitive with people with formal education and more experience"
or
"In n weeks I will have the skills needed to get a job in this field"
Most of the complaining about the program came from the 2nd group. People in the 1st group got better jobs, faster.
Most of those fields seem pretty advanced (can't speak for DSP or trading, but realtime and embedded software both seem fairly intimidating to me). Do you feel that someone totally green to software would be able to ramp up in the time advertised by the average bootcamp (2-3 months)?
Some of your other examples, like lawyers and dentists, however do seem artificial. There is no legal option to hire someone without credentials (at least in the jurisdictions I am close to), even when the buyer understands the risks and poses no external risk to others.
I don't know about this heavy machinery thing. As a farmer, all I need to drive my 30,000 lbs. (when dry) combine down the road is a standard automobile license, and nothing at all once I'm off the public roads. Nobody thinks twice about that. Even more curiously, I do not need any credentials to produce food that people willingly stick into their mouth! You'd think that would be orders of magnitude more worrisome than many of the other careers you pointed out – especially given the difficulty of tracing food origins as a consumer – yet nobody bats an eye.
Computer credentials are also a for-profit business model, rather than an organized body that ensures a certain degree of competency is met. For example, being a board certified physician requires a lot more than simply passing a bubble test, which is what a lot of credentials in the computer industry consist of.
I think credentialing does demonstrate a certain degree of competency, but it also does create an artificial scarcity, since many, many, many people out there have the same skills, or better, but just don't feel the need to obtain credentials.
(C.N.E. = Certified Novell Engineer, but who would know that nowadays, or care?)
1. Credentials Legally Required: Lawyers, Doctors, etc.
Credentials and accredited schooling are required in these disciplines because they involve specialized knowledge AND because misuse or malpractice can seriously hurt people. Even then, there's plenty of cartel-like behavior going on. For example, the U.S. system of accrediting lawyers (three years of graduate school plus bar exam) is almost certainly overkill.
2. Specialized Technical Skills: Welders, Trades
Welding, fabricating, etc. require specialized skills and knowledge. These skills are taught in trade schools and through apprenticeships, not four-year colleges. The credentials are usually not LEGALLY required to work in the area - you can hire a welder who doesn't have one - but in practice, you want to hire people with the credentials because they probably know what they're doing.
3. Non-Technical Skills: Teachers, Social Workers
Teachers, child services workers, etc. Here I think the argument for credentials is the weakest. Why do we NEED accredited teachers? For centuries we've had teachers who never had one, and even now, many private schools don't require credentials. In fact, some of the best teachers I had in school never had teaching degrees - they had degrees and experience in the relevant field (say, chemistry) and came to teach. In fact, in some of these fields, the credentials are attempts to form bars to entry, thus protecting the existing members of the profession - just why do we need school + certificates for hair dressers?
So where does software engineering fall? I think the second category is where it belongs, and bootcamps are attempts to create the kind of technical training / apprenticeship that exists in the trades. That doesn't mean official CS degrees are worthless - far from it - but it also means that we don't need any bars to entry for people who decided to learn coding in another way.
Because there's a need, and that need is vital.
For example, a dentist can take a six-week course on breast augmentations, and then perform boob jobs on the side. There are many "cosmetic surgeons" out there who are dentists, ENTs, and general practitioners, who have no formal training in plastic surgery. That's why it is important to look for a board certified plastic surgeon, rather than a board certified dentist who does plastic surgery.
Collaboration in engineering is hard enough without having to deal with someone that forces a git push, is comically overconfident in their solutions, or exhibits any number of traits I've found to be common from people coming from the "learn a trade in a hurry" programs.