When to create reuseable objects

Could use input on guidelines

[RossWal]

I'm writing some guidelines on when it's a good idea to create reuseable objects in the classic asp and asp.net arenas. In mulling it over, I've come up with surprisingly few thoughts. It's as though I just sort of have a gut feel that I can't quite express in writing.

The thoughts I've hit on so far include discussions about the advantages of reuseability, and secondly how an object oriented aproach can help break down complex problems into more manageable chunks. Surely I'm missing something. Anyone with ideas?

Thanks,
Ross

[NFFC]

>Anyone with ideas?

Don't look at me :)

Anyone?

[Xoc]

I wrote an article on writing large programs for a conference in 2000. It's written for Visual Basic 6.0, but much of it applies to why you'd design for re-use. I just put it on the web to try to answer this question. It's a little long for a post. You can find it here [xoc.net].

A web site is really just a large program.

[RossWal]

Thanks Xoc. Nice article & good food for thought.