From: "Hal E. Fulton" <hal9000@...>
Date: 2001-11-02T13:59:55+09:00
Subject: [ruby-talk:24142] Re: Modularity question

----- Original Message -----
From: Ryan Leavengood <RyanL@mosaicsoftware.com>
To: ruby-talk ML <ruby-talk@ruby-lang.org>
Sent: Thursday, November 01, 2001 2:34 PM
Subject: [ruby-talk:24114] Re: Modularity question


> Well as I continue to learn about XP and try to use its concepts more, I
> can't help but feel that issues like this are cases of BigDesignUpFront.
> Maybe you are trying too hard to predict the future use of your code?

It's a tough call to me.

The "Big Design" syndrome is real, but the opposite extreme is
excessive sloppiness and failure to plan ahead.

I think of it as "prefactoring" -- as far as I know, I made up that
word. No charge for that.

I'm not talking about a gigantic productivity improvement, of course...
I'm talking in the realm of "an hour of prefactoring is worth two hours of
refactoring."

> Of course if one of the explicit requirements is "the application will
> have pluggable interfaces", then maybe this is something that needs to
> be considered.  I'm not sure on that really, since like I said I'm still
> experimenting with XP.  So for any of you XP gurus in the audience: if I
> find myself thinking a lot about some design issue like Hal's, am I on
> the wrong track?

That's an interesting question also. I'm still very much exploring XP, and
I can't say that I am a practitioner yet.

I'm pretty much "sold" on the intellectual concept, but it's not an
integrated
part of my coding life.

Hal