Re: Rapid Application Development
- From: Richard Heathfield <invalid@xxxxxxxxxxxxxxx>
- Date: Sun, 16 Jul 2006 18:26:13 +0000
Ben C said:
On 2006-07-16, Richard Heathfield <invalid@xxxxxxxxxxxxxxx> wrote:
Phlip said:
Richard Heathfield wrote:
Rapid Application Development
Detailed, useful documentation prepared during development
Choose one.
Uh, I sort'a thought there was a third option there. And more rapid...
If you increase the programming effort, you're taking away effort from
the documentation, and vice versa. If you add people so as to try to do
both in parallel, the documenters end up nagging the programmers for
information, slowing both teams down. Fred Brooks covered this some time
ago.
I'm not sure about this. In programming you have to "be slow to be
fast". Taking a bit of extra time to document as you go along may speed
up development measured over the next year or so because the act of
documenting has slowed people down a bit and made them think more about
what they're doing-- so fewer bugs to fix, and clearer code so they're
easier to fix.
Oh, I agree entirely - but that just means you've chosen Option 2 because
you think that it's more productive than Option 1 in the long term. In
other words, you are of the school that thinks "Rapid Application
Development" is a misnomer. :-)
--
Richard Heathfield
"Usenet is a strange place" - dmr 29/7/1999
http://www.cpax.org.uk
email: rjh at above domain (but drop the www, obviously)
.
- References:
- Rapid Application Development
- From: itsyash
- Re: Rapid Application Development
- From: Richard Heathfield
- Re: Rapid Application Development
- From: Phlip
- Re: Rapid Application Development
- From: Richard Heathfield
- Re: Rapid Application Development
- From: Ben C
- Rapid Application Development
- Prev by Date: Re: Randomly outputting an array
- Next by Date: Re: Randomly outputting an array
- Previous by thread: Re: Rapid Application Development
- Next by thread: all in one keygens top 15
- Index(es):
Relevant Pages
|