Date: Mon, 8 Mar 2004 13:33:38 -0800
From: Paul Jackson <pj@sgi.com>
To: Grigor Gatchev <grigor@serdica.org>
Cc: mfedyk@matchmail.com, christer@weinigel.se, linux-kernel@vger.kernel.org
Subject: Re: A Layered Kernel: Proposal
Message-Id: <20040308133338.3837fbf7.pj@sgi.com>
In-Reply-To: <Pine.LNX.4.44.0403081311020.21912-100000@lugburz.zadnik.org>
References: <404BE46F.1000000@matchmail.com>
	<Pine.LNX.4.44.0403081311020.21912-100000@lugburz.zadnik.org>
Organization: SGI
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1277
Lines: 30

> While coding, think coding. While designing, think designing. Design comes
> before coding; otherwise you design while coding, and produce a mess.

You are describing, roughly, the waterfall model of software development.

Linux kernel work is closer to something resembling the prototype
and/or spiral model.

See further explanations of these terms, for instance, at:

  http://model.mercuryinteractive.com/references/models/

But, in any case, Linux kernel work _does_ have a rather extensively
articulated development model which we find is working rather well,
thank-you.  For all I know, this methodology was defined by some
traumatic event at the birth of Linus - whatever - seems to work.

When in Rome, do as the Romans.  And especially don't be surprised
at being pushed aside if you protest that we aren't behaving as the
French.

-- 
                          I won't rest till it's the best ...
                          Programmer, Linux Scalability
                          Paul Jackson <pj@sgi.com> 1.650.933.1373
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/