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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Switching to Discord

1 点作者 hampelm超过 6 年前

1 comment

Pinbenterjamin超过 6 年前
Solid self-awareness here by the team at Streetmix.<p>It&#x27;s touched upon in the sentence;<p>&quot;Discord, unlike Slack, is not as well-known in the corporate world. Although marketed to gamers as a voice chat alternative, its core service (much like Slack’s) is the chatroom.&quot;<p>Slack is a pretty solid solution for large enterprise teams, needing support for different parts of their organization. It&#x27;s akin to a &#x27;living wiki&#x27; of sorts.<p>Discord is much more ad-hoc, and less feature rich, which makes it a better place for smaller teams with a need purely for communication and coordination.<p>There are great collaboration tools that I could envision discord working with, for smaller teams. Like VSCode&#x27;s Code Share.<p>My critique of these services in general comes in the same flavor that my &#x27;open office&#x27; argument does. Lines of communication are critical, but should be used judiciously. Everyone available all the time for conversation and questions, without recourse, can lead to the type of environment where everyone holds knowledge in their head, instead of writing it down, or documenting it.<p>I&#x27;ve always believed that the best tool we have now are scheduled, web-based team meetings with screen sharing. They have to be scheduled, and one person is always leading a topic. It&#x27;s targeted, and there is usually a goal. Concise. I&#x27;ve always liked that.