Discord is not documentation (shkspr.mobi)

Article summary

The article discusses the limitations of using Discord as a substitute for documentation, highlighting the difficulties of finding relevant information in a chat-based platform. The author argues that Discord is not a suitable replacement for proper documentation, citing the lack of organization, search functionality, and permanence of information. The article also mentions the frustration of having to scroll through numerous messages to find answers, only to discover that the information may be outdated or irrelevant. The author concludes that while Discord can be useful for ephemeral communications, it is not a viable alternative to well-structured documentation.

Main themes

• Discord as documentation
• importance of documentation
• user experience
• generational preferences
• software industry trends
• trust and adoption

What commenters say

• Some commenters argue that the trend of pushing everything to Discord, including support, is an awful experience for users, while others see it as a convenient way to engage with customers.
• The effectiveness of documentation depends on its quality, with some arguing that good documentation can reduce the need for support, while others believe that people will always ask questions regardless of the documentation's quality.
• There is a perceived generational divide in the preference for documentation, with some believing that younger users prefer interactive platforms like Discord, while others argue that this is not a valid excuse for lacking documentation.
• Some commenters suggest that the lack of documentation is a result of the fast-paced nature of the software industry, where products are frequently updated or replaced, making it difficult to maintain accurate documentation.
• Others argue that documentation is essential for building trust with users and that its absence can lead to frustration and a lack of adoption.
• A few commenters propose alternative solutions, such as using Discord as a supplement to documentation, rather than a replacement, or implementing AI-powered chatbots to help users find answers.
• The discussion also touches on the idea that people may not read documentation, not because it's poorly written, but because they are in a hurry and prefer to find quick answers through other means, such as searching online or asking in chat forums.