From: Clinton Bunch <cdb_zsh@zentaur.org>
To: zsh-users@zsh.org
Subject: Re: Tagged parameters
Date: Thu, 17 Aug 2023 18:41:02 -0500 [thread overview]
Message-ID: <d20b23d3-9b98-28d1-7415-589fe36f8d66@zentaur.org> (raw)
In-Reply-To: <a64aac70-976f-24c6-a24a-ad766d13485d@tnetconsulting.net>
On 8/15/2023 17:41, Grant Taylor wrote:
> On 8/15/23 1:10 PM, Ray Andrews wrote:
>> The problem of manuals being written by people who are already
>> experts is always hard to avoid.
>
> Who would you suggest write about ${TOPIC} if not someone that has
> already learned about ${TOPIC} and ostensibly has some level of
> mastery / expertise thereof?
>
>> Manuals must serve the person who is not already an expert and that's
>> difficult because the minds are different.
>
> I don't agree.
>
> Documentation, of any sort, is better than no documentation.
>
> N.B. I don't consider source code to be documentation that is
> accessible by most people.
>
> Yes, there is some documentation that tends to qualify as more
> reference material and other documentation that qualifies as more
> teaching material. Traditional manual pages are often an example of
> the former. While Ho-To guides on The Linux Documentation Project tend
> to be examples of the latter.
>
> I believe there are places for both types of documentation. What's
> more is that neither type of documentation precludes the other from
> existing.
>
> I would much rather have something terse, dense, and quick from a
> programmer that doesn't have time to word smith than not have even that.
>
> Others who don't feel comfortable can take the snippet from the
> programmer and turn it into more friendly if not training friendly
> documentation.
>
I always thought that was what technical writers were for.
Of course, we could always hand it to ChatGPT to write the Zsh manual :)
next prev parent reply other threads:[~2023-08-17 23:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 5:51 Marlon Richert
2023-08-15 8:27 ` Peter Stephenson
2023-08-15 14:30 ` Ray Andrews
2023-08-15 14:39 ` Peter Stephenson
2023-08-15 15:16 ` Ray Andrews
2023-08-15 17:40 ` Lawrence Velázquez
2023-08-15 18:10 ` Ray Andrews
2023-08-15 22:41 ` Grant Taylor
2023-08-17 23:41 ` Clinton Bunch [this message]
2023-08-18 1:10 ` Bart Schaefer
2023-08-18 4:15 ` Ray Andrews
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d20b23d3-9b98-28d1-7415-589fe36f8d66@zentaur.org \
--to=cdb_zsh@zentaur.org \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).