From: Christopher Smith <[EMAIL PROTECTED]>
Andrew Lentvorski wrote:
The real slowdown comes when you shift from clean slate development to
maintenance. I can write 100+ lines of code per hour when I start out.
However, then I start having to debug things. Suddenly, my lines of code
per hour drops like a stone.
Maintenance always means fewer lines of code,
Not in the least. Take the following sets of code:
while(*x!=0)
*x++=*y++;
or
i=0;
while(x[i]!=0){
x[i]=y[i];
i++;
}
The second is more lines, but also more readable. I'll take it any day of
the week. This is a simple example, but its not uncommon. For another
example, I'd rather see a perl program add 10K lines and use explicit
variables than depend on the magic $_.
In general, I don't see why you'd think that XP would be particularly bad
in this mode.
Lack of documentation. Lack of real design or design documents. Code thats
constantly in flux, leaving it hard to find a dev that understands most of
it. Cruft and hacks from trying to make a two week milestone, rather than
spending time to do things the right way. I'd maintain a program under any
other process, including the much maligned waterfall, before I'd touch one
done by XP.
Gabe
_________________________________________________________________
Get the latest Windows Live Messenger 8.1 Beta version. Join now.
http://ideas.live.com
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
