Developer Book Club
henrikwarne.com
henrikwarne.com
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.
It's also possible that purely language/framework books don't work as well. Code Complete is good because it gets people talking about architecture, general best-practices, and career mastery. ng-book only gets people talking about the framework.
To revive ours, we've discussed reading relevant articles rather than entire books.
That has been my experience. The best book club discussions (we do probably 10 different groups a year for 5+ years at this point) have been for books like The Pragmatic Programmer, Rework, Lean Startup, etc -- ones that focus more on a methodology or have room for discussion about trade-offs. Framework/language specific books tend towards the reference material side of things and don't have much room for discussion. One exception is the Seven Languages in Seven Weeks book -- we would work the exercises on our own and then meet together to discuss and share our solutions.
Not trying to promote (most people probably know NGINX and you can ask not to be contacted about our commercial product), but it's a great book, just started here 2 months ago and it was a great book to help with here, as a lot of discussions we have are moving to MicroServices.
Here's a link. https://www.nginx.com/blog/building-microservices-free-ebook...
We're too geographically distributed to do this effectively in our off hours, unfortunately.
I found it a super positive experience, as we had a chance to reflect on our team in the context of "established" best practices and look at what aspects of their process made sense to apply to our organization. Also, that book is quite good and it was fun to have some pressure to read a couple sections every week.