Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I don't think this is WordPress employees taking a mile when given an inch by working remotely all the time. I believe WordPress encourages employees not to regularly go to the office. The reason being is they don't want a small faction of the company to become essentially collocated while the rest of the company is distributed, thus breaking their communication flows. Remote works for WordPress because almost all communication gets archived in Slack, email or p2 (their internal social network built on WordPress). Anyone can see what's going on or get caught up asynchronously. It's pretty much guaranteed that in a collocated environment some of that communication would happen offline IRL, and others would miss out on it.


"archived in Slack"

Wait, is there a way to make old conversations in Slack less painful to find and read? Anything more than 3 pages away is just not worth the effort for me.


I typically use the slack app to find conversations I want to read, and then if they're more than a few pages in the past, will read them in the web interface. The web interface seems somehow to perform many times better.


These guys are building a business in this space: https://slackarchive.io/

The claim to fame so far is free archiving for public channels, often useful for open source projects that have accepted the trade-offs that come with directing a community to a free public slack.


use the IRC bridge and log in plain text ;)


http://slackarchive.io/ is neat, you might be able to get utility out of that, depending on what you're doing.


Search


Searching in the app is brutal, and if you are having a conversation in the same channel, it's basically worthless.


Have you tried in:<channel> <search query>? Seems to work ok for me. Similarly, using from:<user> <search query> is useful.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: