That's a far cry from learning what it takes to create quality software.
Sure, that doesn' t mean they are useless... Sure, if you pay them a regular tech-salary...
But can you have second-class developers in a company?
For example writing tests, or internal web applications based on rock solid automation APIs. Or web-based dashboards for presentation of metrics collected and exposed through a stable APIs...
I 50-75 % of study points for my MSc in CS comes from or is related to large group projects. As someone who is smart and skilled, I quickly learned how to isolate parts of the project and hand out smaller isolated pieces. Typically, just implement a strategy pattern, then tell someone write a strategy or two that filled the interface of my strategy. In the meantime I could rely on a strategy with a bare minimum implementation, for example hard code input instead of loading from file, accepting memory leaks, accepting poor performance.
It's not always easy to use people with limited skills, but it's not impossible. Though you obviously don't get the same results.
On the other hand, I have an MSc and is super generalist, and sometimes I'm wasting my time writing simple things in node.js, not that everything in node is simple :)