Agreed. Trying to find answers for questions probably already asked on Discord is impossible.
this post was submitted on 28 Jul 2023
837 points (98.9% liked)
Programmer Humor
33533 readers
320 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
And then some uppity moderator of some Discord channel for a niche mod for some game gets pissed at users for asking the same question repeatedly, when it's not obvious at all from any non-Discord source.
Looking at you, Our Summer Car -_-
I'm not 41 yet, but even if you csn somehow make a chat room app replace the functionality of code documentation or a few simple example code snippets... should you? You're also hosting on GitHub and not on MEGA, even though you could...
Fuck Discord.
It's great for what it's intended for, a gaming voice/text chat server.
load more comments
(1 replies)
Seriously fuck discord
load more comments
(3 replies)
So much yesss, that drives me nuts, regardless of age!
I know that it's just hip and familiar to many, so I put with it with the few projects I'm really interested in and I can't say it doesn't work well, but please, why are there SO MANY??
For open source, I almost always found IRC was a black hole of information. All kinds of developers discussing things that never made it to search engines. It's a long tradition.
As a dev, far easier to answer questions about my code than write up documentation, so makes total sense to me
With discord at least you can usually search chat history for your question and find someone else asking it in the past
I wonder... Might be able to write a language model based crawler that goes through a discord server and pulls out all the useful information to generate documentation or at least a FAQ
To be fair, a discord comment from five years ago is still more helpful than Amazon AWS's actual documentation.
load more comments
(1 replies)
I'm usually on the documenting side of things. If something like this starts unfolding, I produce text or HTML files anyway, they go on github/lab/whatever, and I wash my hands of what happens next.
In the end I write documentation mostly for myself. When the company can't figure things out over Discord or whatever ephemeral chat interface they use, I get called anyway.
> I produce text or HTML files anyway
I do extensive in-code documentation. The compiler discards all comments so I don't worry about commenting my code. Source code is for humans to understand and write anyways.
Oh, yeah. My source code is like 60% comments by weight (or more). Although I typically produce separate standalone documentation for management or semi-technical staff. You know, people who know enough to possibly break something, but not enough to fix it afterward. I find it useful when trying to train new people too.
User-facing documentation is a completely different thing, yes.
load more comments
(1 replies)