this post was submitted on 12 Oct 2023
1266 points (98.5% liked)

linuxmemes

20829 readers
1355 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Aceticon@lemmy.world 13 points 11 months ago* (last edited 11 months ago) (1 children)

Oh, you sweet summer child, there is no level of ease for the average programmer that will make him or her want to document things... ;)

On a more serious note, good documentation for parameters in any tool that's not stupidly simple tends to be more than a one liner if one doesn't assume that the user already knows a ton of context (for example, imagine explaining "chmod" parameters with just one liners)

[–] taladar@sh.itjust.works 2 points 11 months ago (1 children)

You can write more than one line but one line is usually enough for each of the options in the --help output. Obviously that doesn't explain everything and especially not background like "how do unix permissions work" in your example but the --help output is not the correct place for that kind of information anyway.

[–] Aceticon@lemmy.world 2 points 11 months ago* (last edited 11 months ago)

The point is that a programmer would first need to think about what needs to be explained or not to the average user and then explain it properly, none of which is considered as interesting as coding.

It's not by chance that even tools with actual one line of explanation for each parameter are general of the badly documented kind (I especially like the ones were the "help" for a command doesn't say what the bloody command actually does).

I mean, you even see this kind of meaningless "documentation" in API documentation for widelly used libraries were the documentations is generated from comments embedded in the code: "public void doStuff(int height)" => "Does stuff. Parameters - height: the input height".

I might have put it in a humouristic way but this quite a well-known and widespread phenomenon.