Re: Full life cycle development

H. S. Lahman wrote:

> Basically I agree with Phlip (except for the Waterfall part) that this
> is most common view.

I am aware that iterationists use the "Waterfall" bugaboo to illustrate
by high contrast, and if this contrast alone links an argument then
that might fall to the fallacy of the strawman.

However, in real life, developers who are not as smart as you or I tend
to re-invent Waterfall naturally. They code-and-fix, discover new
requirements, and discover their code is now brittle. So they say, "The
next time, we will gather all the requirements first, before we start."

I have heard them say exactly that, with my own ears.

> ...The fallacy is that the maintenance cycle
> tends to be much longer than the original development cycle so the
> superstars are stuck doing the boring stuff too long and they go away
> anyway...

This superstar often gets stuck not being allowed to automate the
boring stuff, and not allowed to collaborate in a way that would
sustain the automation of the boring stuff. Not everyone likes to learn
Lex & Yacc just to avoid tweaking the same dumb C# file every other
day.

--
Phlip

.

Relevant Pages

  • Re: Tips for improving skills at interpreting other peoples code?
    ... Phlip said: ... Waterfall works fine, if you have the right people. ... In fact, just about /any/ methodology works fine, if you have the right ... rjh at above domain ...
    (comp.programming)
  • Re: Waterfall Photography
    ... and see how many THOUSANDS of stupid waterfall photos there are. ... THEY'RE BORING AND TRITE! ... Please feel free to join and discuss waterfall photography techniques ...
    (alt.photography)