this post was submitted on 10 Jul 2023
855 points (97.7% liked)

Programmer Humor

32549 readers
350 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] r00ty@kbin.life 19 points 1 year ago (1 children)

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.

[โ€“] Kryomaani@sopuli.xyz 10 points 1 year ago* (last edited 1 year ago)

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.