TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Using Slack for #engineering-team-group-therapy

5 点作者 annamarie大约 10 年前

1 comment

potench大约 10 年前
You can see your company&#x27;s Slack stats here <a href="https:&#x2F;&#x2F;[your-company].slack.com&#x2F;admin&#x2F;stats" rel="nofollow">https:&#x2F;&#x2F;[your-company].slack.com&#x2F;admin&#x2F;stats</a> For example at work we noticed a high number of DMs (&gt; 80%) and we&#x27;re trying different things to bring that number down to promote more transparency, collaboration, and opportunity to impact decisions across the team.<p>Department-channels (#backend, #web, #ios) can get pretty chaotic with multiple threads getting discussed concurrently. I can see how a topic-channel (#android-release-process) would help you swarm more efficiently. But, making it private and inviting only those you think should be there seems counter to the goal of transparency and &quot;swarming&quot;. Maybe you could originate these topic-channels from a general channel with &quot;@group, we&#x27;re swarming on #android-release-process&quot; and make it public.