On Sun, Sep 03, 2000 at 09:05:07PM -0700, Russ Allbery wrote:
> I also think this may well be a good place to apply one of the ideas of XP
> (Extreme Programming, a fairly flexible small-group software design
> methodology), namely to write test cases *first* in many cases before
> writing the code, and to seriously consider trying to write unit tests for
> pretty much every bit of code that you write.
This is the way I commonly program as well. I tend to write docs
first, then code, then tests in an interative loop, building up the
program as I go along and testing as I go. While most people give
lip-service to this style of programming, its real use in practice
seems rather limited. If we do go this route, we're going to have to
do alot of teaching of the practical aspects of this style. And its
going to require alot of cajoling to keep the grumbling to a minimum.
I wrote a proto RFC on this subject a few months ago ("RFC: A Test For
Every Patch") and Ziggy and I discussed the bare bones of it at TPC.
I'll dust it off and resubmit it in the proper format.
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid Consultant Perl6 Kwalitee Ashuranse
you're a bleeding-heart
liberal. LET ME PLUG MY
ASS WITH PASTE RIGHT NOW!
-- japhy
