I recently quit my old job which was desperately trying to claw employees back into the office (first 1 day a week, then 2, then 3) for a fully remote role. It’s been a breath of fresh air. My new team is spread all over the country and yet everything runs so much more efficiently compared to my old employer.
They do have a small office available in case anyone prefers that environment (or perhaps their home isn’t suitable for remote work) but there is no expectation or requirement to come in, other than a suggestion that each team meets face to face maybe a handful of times per year, if only to get lunch/drinks together or have a social day.
It’s working out great for them as it lets them scale the number of employees they have significantly while not spending any more on commercial real estate.
It’s been pretty good. I have noticed the default sort order (‘Active’) results in the feed getting stale pretty quickly. Changing the default to ‘New’ has been a better experience so far, at least at the current level of activity.
I have had a few issues subscribing to communities on remote instances (i.e. not showing up in search, or showing up but with an empty feed when content definitely exists when I check the web UI) - this does not appear to be an SFW/NSFW issue, and some communities from the same remote instances appear correctly.
Hard to tell if this is an instance/protocol issue, or an app issue.