Live data from Hacker News

Slack Shared Channels

slackhq.com

51–60 of 72 posts

Re: Slack Shared Channels

#51
post #9

Looks like they're finally available for enterprise grid customers too! Last time I checked it was only for standard plans.

Strange - I was using Shared Channels on an enterprise grid plan over a year ago...

For a long time you could use them within a grid, but not between a grid and the outside world.

Re: Slack Shared Channels

#52
This is a handy time to mention that my employer makes a Slack app for shared channels that provides support-like operational assistance and analytics.

We’ve helped a lot of companies, especially serious tech/infrastructure companies, manage dozens of active channels with their most valuable customers. They also use it with internal-facing “escalation” channels to facilitate collaboration.

On the operational side it uses PagerDuty-like notifications, state management, open convo reminders, and webhook integrations.

https://frame.ai/frame-for-slack

Re: Slack Shared Channels

#53

“New people coming into a project can readily access a project’s archive, allowing them to ramp up swiftly.” How many people have ramped up quickly by reading the chat history of a channel? That’s not documentation—instead it’s like a really bad screenplay. I hate digging through channel history as I join and kinda resent the expectation that I’m supposed to do that.

Slack history was invaluable to me when I was ramping up at my current role. You get a real sense for the struggles the teams are dealing with.

Re: Slack Shared Channels

#54
post #8

The issue with the channels are the same than communicating over slack: You customers are feeling like they can ask any question and get an answer in 1 minute, and if you dont answer them straight away then they are unhappy. Definitively not something I recommend

We combine Slack + Zendesk for this reason. Users can start however they like + we can pick to shift. Enterprise SLAs are generally 1hr for ack anyway, and early stage needs to be customer centric, so works great in these settings.

Re: Slack Shared Channels

#55

“New people coming into a project can readily access a project’s archive, allowing them to ramp up swiftly.” How many people have ramped up quickly by reading the chat history of a channel? That’s not documentation—instead it’s like a really bad screenplay. I hate digging through channel history as I join and kinda resent the expectation that I’m supposed to do that.

Unfortunately Slack is where documentation goes to die. When I face a weird internal issue the first thing I do is search:

> in:@

You would be amazed at how much unofficially documented stuff is sitting in Slack. It is unfortunate but paying attention to the right Slack channels at work can be very important in understanding company strategies and decision making, as well as random tidbits on architecture decisions.

Of course I would prefer official documentation but sometimes you gotta make do.

Re: Slack Shared Channels

#56
post #55

“New people coming into a project can readily access a project’s archive, allowing them to ramp up swiftly.” How many people have ramped up quickly by reading the chat history of a channel? That’s not documentation—instead it’s like a really bad screenplay. I hate digging through channel history as I join and kinda resent the expectation that I’m supposed to do that.

Unfortunately Slack is where documentation goes to die. When I face a weird internal issue the first thing I do is search: > in:@ You would be amazed at how much unofficially documented stuff is sitting in Slack. It is unfortunate but paying attention to the right Slack channels at work can be very important in understanding company strategies and decision making, as well as random tidbits on architecture decisions.…

The alternative in most cases is _no documentation at all_. It's not like people would go spend two hours writing up documentation if Slack didn't exist.

Re: Slack Shared Channels

#57
post #55

Earlier quoted context omitted.

Unfortunately Slack is where documentation goes to die. When I face a weird internal issue the first thing I do is search: > in:@ You would be amazed at how much unofficially documented stuff is sitting in Slack. It is unfortunate but paying attention to the right Slack channels at work can be very important in understanding company strategies and decision making, as well as random tidbits on architecture decisions.…

The alternative in most cases is _no documentation at all_. It's not like people would go spend two hours writing up documentation if Slack didn't exist.

In large teams it's worth the reduction in 'code velocity' to have engineers document what they are building.

I specifically make efforts, and encourage others to do the same, to keep most documentation outside of slack. Do you have a question about a ticket? Ask it in a comment not slack. Do you have a question about how our system works? Ask it in the private Stack Overflow. Want to advertise a cool new internal service we can use? Great tell everyone in slack, but also add it to swaggerhub.

Re: Slack Shared Channels

#60
post #23

I love using discord for my open-source projects as I feel that the individual role and channel permissions are a little more powerful. I wish Slack adopted this full customization permission ability into their software.

Hard to imagine using Discord for open source projects, but this is likely all marketing/branding association for me. That said, I can see the appeal. Definitely one of my favorite pieces of software these days.

Rust and React are on Discord, you should check them out, seems to work pretty well
Post reply on HN