From: ken <gebser@mousecar.com>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs documentation: what's active voice, passive voice?
Date: Fri, 10 Dec 2010 11:04:29 -0500 [thread overview]
Message-ID: <4D024F8D.8060707@mousecar.com> (raw)
In-Reply-To: <87aakee8bm.fsf@gmail.com>
On 12/09/2010 08:16 PM Sean Sieger wrote:
> There is no royal road to writing, like Math. To write better, read more.
> Read, re-read, re-re-read, and read better what you've written (and
> rewritten...).
>
> Right?
>
> I always thought `reading is miswriting and writing is misreading'
> instructive.
Good advice. And it applies to a lot more technical documentation than
just what's done for emacs.
There's a very old saying among writers: Writing is rewriting. Yeah,
that means more time and work than just dashing off a first draft. But
the benefits are worth it.
One technique for better documentation is to give your first draft to a
newbie and have him/her work from it. That newb will notice any holes
or ambiguities and other failures in the text; these are then added into
the doc. This amended doc would then be passed on to another newb and
the process repeats repeats until a newb has no more questions or
failures. A wiki is a good platform for this kind of process.
next prev parent reply other threads:[~2010-12-10 16:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 3:06 emacs documentation: what's active voice, passive voice? Xah Lee
2010-10-03 11:14 ` Uday Reddy
2010-10-03 19:29 ` Russ P.
2010-10-03 19:38 ` Jay Belanger
2010-10-03 20:50 ` David Kastrup
2010-10-03 22:57 ` Russ P.
2010-10-04 18:48 ` Alan Mackenzie
2010-10-05 0:53 ` Russ P.
[not found] ` <ias317$dtr$2@reader1.panix.com>
2010-11-04 19:22 ` Stefan Monnier
2010-11-04 20:10 ` Pascal J. Bourguignon
2010-12-09 17:48 ` Drew Adams
2010-12-10 1:16 ` Sean Sieger
2010-12-10 16:04 ` ken [this message]
2010-10-03 12:47 ` Bruce Stephens
2010-10-03 22:07 ` B. T. Raven
2010-10-04 6:52 ` David Kastrup
2010-10-05 4:02 ` B. T. Raven
2010-11-03 16:34 ` David Combs
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=4D024F8D.8060707@mousecar.com \
--to=gebser@mousecar.com \
--cc=help-gnu-emacs@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.