> 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.
@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 @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.
