So first you say that boot camps get it wrong and computer science programs get it right "by teaching algorithms first." Then you talk about the CS student also getting it wrong (with a project he probably won't need algorithms to solve). The issue is not that junior devs are not being taught algorithms, but that they are being taught by people who don't have the COMBINATION of skills needed to teach them: both an understanding of what it really takes to build working software and an understanding of how to break those skills down into pieces someone who knows nothing can easily understand and incorporate into a working mental model. This is a sticky wicket, because if you're working full-time as a developer you probably don't have the time to develop pedagogical skills or write a curriculum, and if you're not working full-time as a developer, you're probably getting rusty in some aspect of what it takes to build working software.

This is exacerbated by the fact that most senior devs do not know how to break their software out into pieces that even a beginner coder can pick up and work on, so most juniors get thrown in to sink or swim without an easy onramp.