I'm gonna do some exploring and write a blog post about this!

@hamatti Another option would be to have a shared web-based dashboard type of page that would list latest blog posts from those 3rd party blogs (and other feeds). That way people wouldn't even have to maintain their own feed readers, because latest posts and links could be read from the central location.

@hamatti Yeah, but how many still use feed readers? If the goal is the get the full team to look at those, path to least resistance is to avoid requiring people to start running yet more applications.

OPML file can be same in both, but example stands. (There are that kind of simplified RSS feed headline display tools from various people on GitHub.)

@autiomaa I get the mindset of least resistance but I also feel that people who already don't follow articles and resources are likely not going to pick up visiting new websites regularly to read stuff.

This thought experiment is more about implementing this in an environment where people are already interested rather than trying to get people who aren't to start being interested.

@hamatti For sure, if you have such a great luck to have such a team. But when people change projects and teams, how often all of the team members have so much extra time to keep up with the scene, if work schedules don't have enough flexibility for the learning? Not everything can be outsourced to personal learning time outside of the work, if it is directly related to the work.

My main worry is that while this kind of shared RSS feeds could be useful for improving learning in a longer term (product/service focused) teams, it likely wouldn't work that well in a consultancy environment where people come and go constantly from one project to another (with completely different technology requirements).

@autiomaa

> Not everything can be outsourced to personal learning time outside of the work, if it is directly related to the work.

I had no intention to indicate that these would be read on free time. A shared team feed would be a good way to build culture where these things are considered valuable for the work and thus something that is expected to at least keep an eye on during work hours.

For this reason, it should also be very heavily curated to only have essential stuff.

@autiomaa And you're right that in short-lived teams in consulting this would make less sense.

In long term projects though, it would be a great way to codify what the team considers valuable for the project and a new person joining the team could just sub to the shared feed instead of everyone having to figure things out on their own.

@hamatti One rather relevant type of feed would be software/component version updates. From GitHub or elsewhere. That would directly help people to get a feeling how often those parts get updated that they are using as part of their work.

@autiomaa Exactly! Subscribing to release notes for libraries that the product relies on or tools and services the team uses would be a great way to help everyone stay updated on what's happening.

I often feel like the odd one out as someone who likes to read release notes though.

@hamatti I remember back in 2002 when one co-worker pointed out that he never updated software on Linux servers without reading changelogs. He was actively worried of people automatically updating *anything*, because of the practical experience of how often software updates broke something essential.

Yes that was ~22,5 years ago, but not that much has changed with how well/badly people read the changelogs.

@autiomaa For tools, I mostly read them so I don't miss any amazing new things.

These days, software rots so fast if not updated that there's very often no real option to not to.

@autiomaa @hamatti at one work place we had something like you described. It was a third party service but with closed and private access...

I wonder if an unfederated corporate network Lemmy + some bots would be an easy way of doing this now?

@nemeciii @hamatti Lemmy might be overkill for that. I think there are a lot simpler options for the relatively simple use case.

@autiomaa @nemeciii Yeah, I'm not sure if there would be much of benefit from all to social features of Lemmy for something I envision to be "read online, discuss in person" type of deal.

Internal discussion forums are an interesting alternative or addition to intranets but I've yet to see them be functional as most people don't bother reading or writing to them.