[ska]

> Are you able to organize that on company time? Are you guys clocked in during your meetings?

I've approved or started (or both) this sort of thing on company time before, at more than one place.

For context, this was typically early stage R&D, and many/most of the employees had some academic background, though that ranged from "decades ago" to "we just hired you after a masters degree".

In this setting, it's a pretty natural continuation of the common "journal club" approach in academic research groups. It spreads the effort around, helps the team stay on top of new work, and generally improves professional development - if done well. It does take a bit of effort to keep fresh.

[jll29]

I think most technology companies should have that, and I've been promoting that workplaces.

The trick to make it sustainable is to make at 3-month calendar of covered papers from multiple sub-areas (e.g. data management to machine learning, new programming languages to compiler topics) and share that widely. Not every topic is relevant to everyone, so naturally each topics will only attract a subset of the crowd beyond a small number of open-minded champions, but that's okay.