It's important for younger devs to first write bad code to learn about why it's bad. I agree that the books probably won't be of much use for a starter because you first need to gather experience before you can learn from it.
You probably need to hire brighter devs then. The good 'junior' devs (hate the phrase) I've worked with no what bad code looks like already.
So if you want to go on a polemic level: why are your "brighter" Devs Juniors then?
Mire seriously, I would argue, you need decent experience to tell good and bad code apart.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.