From: Mika Liljeberg <Mika.Liljeberg@welho.com>
To: linux-kernel@vger.kernel.org
Subject: Re: White Paper on the Linux kernel VM?
Date: Fri, 25 Jan 2002 18:51:49 +0200 [thread overview]
Message-ID: <3C518D25.F8062F2B@welho.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0201241312450.32617-100000@imladris.surriel.com> <3C50827F.F425DDF2@welho.com>
> Writing about not writing docs wastes everybody's time.
For the record, I would love to see some proper documentation on the
current VM. While the code is indeed the ultimate reference, it does not
yield readily to peer review.
That said, I don't think much of the waterfall model. It tends to kill
the enthusiasm and slow projects down to a crawl. The thing is to write
the code, hone it until you're happy with it, and then document it. If
the code isn't ready to document, it's not ready for peer review. Prior
to that degree of readiness, too many brains plucking at the code just
slows things down. On the other hand, if you leave out the documentation
altogether you end up with developers arguing about who can't read whose
code, instead of doing something useful.
I seemed to touch the hearts of a surprising number of people with my
thoughtless little remark. No permanent heart ache, I hope. :)
MikaL
next prev parent reply other threads:[~2002-01-25 16:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 3:36 White Paper on the Linux kernel VM? info
2002-01-24 6:54 ` David Beckett
2002-01-24 12:05 ` Rik van Riel
2002-01-24 12:59 ` Dave Jones
2002-01-24 16:06 ` Denis Vlasenko
2002-01-24 12:21 ` Rik van Riel
2002-01-24 15:06 ` Olaf Dietsche
2002-01-24 15:13 ` Rik van Riel
2002-01-24 16:40 ` Richard Gooch
2002-01-24 21:54 ` Mika Liljeberg
2002-01-25 16:51 ` Mika Liljeberg [this message]
2002-01-24 18:21 ` Daniel Phillips
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=3C518D25.F8062F2B@welho.com \
--to=mika.liljeberg@welho.com \
--cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox