We didn't introduce books to read at our company, but we did start what we call 'dev learning sessions'. Once a week, one of the developers (it cycles by name)

We didn't introduce books to read at our company, but we did start what we call 'dev learning sessions'. Once a week, one of the developers (it cycles by name) has to prepare and present about a topic approved by an architect (pretty much as long as it might be used somehow at work, it's approved). Then everyone spends about an hour learning about something. Sometimes it's something internal, but often it's a deeper dive into a particular topic regarding database, language, or sql features. We've been doing it for about a year now, and it's getting harder to come up with new topics, but overall it's worked out pretty well. It ends up that you have to give a presentation about once every three or four months. Personally I've learned quite a bit that I probably wouldn't have otherwise, even when I was the one giving the presentations. When it's your turn it can take up to a full day to research and prepare the presentation though, especially if you want to have working source code and it's about a topic you're not too familiar with.