Few hours of surfing on stackoverflow can save you from 5 minutes of reading a documentation
this post was submitted on 10 Jul 2023
51 points (96.4% liked)
Programmer Humor
32453 readers
985 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
StackOverflow is good for:
-
general questions (when you don't know where to look for) eg. how do I go about ...?
-
specific questions (when you know what you want, in simple english) eg. suggest ways I can ...?
-
quick fixes with more than one suggestion eg. I get this error, how to fix and please explain.
-
understanding concepts as different people explain concepts differently eg. what is ...?
Documentation is good for:
-
details (when you need to know more and when you really know what you need)
-
features (find a list when you want to know what else you can do with it)
Another thing stackoverflow is good for is if you're like 14, don't really know programming that well and can't quite comprehend what you're doing but know how to copy and paste code then fidget around with it until your ide stops complaining and it compiles and all works together.
I'm offended you think I'm 14
Sure looks like the left way
Looking at you, Docker compose files.
Docs: "make a docker-compose.yaml, it's so easy!"
Me: "How?? Where?? What's the syntax?? ANYTHING AT ALL?"
Some corner of a dusty website only three people have visited in the last two years: "here's the syntax you need to use for these specific use cases, and you can put it anywhere as long as it's consistent"
Jesus Fucking Christ is it really that difficult to be a little more specific with this kind of thing? This is why I didn't start using Docker until very recently. Their docs absolutely suck balls for someone who isn't already familiar with it.
To be fair, documentation is very often a much longer route to understanding your specific use case. At the same time, SO is responsible for far too much cargo cult programming and I fear ChatGPT will be the same for this.
And there are way too many projects where the documentation is nonexistent or bare to the point of being counterproductive to wade through. I've seen way too many open source projects that purport to have documentation but when you open it, it's just doxygen run over the raw source files with barely any documenting comments in them. If I wanted to see only the names of the classes and functions I'd just pop the source in an IDE, the point of documentation is to point out everything that isn't immediately obvious just looking at names and to give examples.
"Self-documenting code" is the biggest lie we tell ourselves to get out of writing actual, necessary documentation.