I'm also a reader, and in my experience devs who don't feel comfortable with reading (most of them) tend to get better information flow through talking, unfortu

I'm also a reader, and in my experience devs who don't feel comfortable with reading (most of them) tend to get better information flow through talking, unfortunately they're about as likely to be shy as other devs and sometimes don't get a lot of professional development because of this. Get in the habit of talking to them about code casually. ("Have you seen the X library", "I implemented another splay tree today, whoah!") I also send juniors youtube links unless they've expressed they don't like video, there's now a bunch of solid technical content there, better than books in terms of being up to date I would say. A ton of people watch videos sped up 1.75x or 2x, and young people often are in the "classroom" mindset that everything where they are a passive receiver is made of gold and benefit from being explicitly told they can skip parts, watch vids out of order, speed up and then slow down, etc. This may help conserve his time.