>> but professionals, they are not

This is exactly correct. And if you're interviewing juniors/graduates trying to find "professionals" then you really don't understand hiring.

"We're looking for professionals with no commercial experience." It's a contradiction in terms.

BS.

For a corporate setting that may have the resources to hire people for the potential and long term maintenance of their cogs, sure, hire "recent graduates" with zero ability to produce any value to the company.

But don't tell me that you can't find young people with little to no experience that are talented enough to run circles on any "experienced professional" and actually be useful from the start. I've done it myself more than once.

So you want to pay someone to train them.

Why not? That's how it used to work. Provided they can demonstrate a minimum of CS fundamentals, things like tools (git, ssh, etc.), how to work with a large code base, good style, and any number of things that a new grad needs to know to become a competent junior engineer can be taught.

I think this is exactly what the original comment was taking issue with for the bootcampers.

>but as soon as you threw any real world problem that required any deviation from their established lane they completely floundered

He quoted it himself, but failed to notice the issue. I myself have noticed people who went through 4 year programs tend to be much more adaptable as the universities tend to do a better job of building a solid foundation.

Absolutely agree. Juniour doesn't mean "without experience". I will venture far enough as to say that a juniour developer should have very solid tech skills and real world experience.

I've known many people myself included who had 1-2 years of professional experience by the time they graduated from university. And naturally these folks would hit the ground running when hired post graduation, which is as it should be.