Here's another thought. Code Complete says "Construction is the only activity that is guaranteed to be done. *snip* Improving construction is thus a way of improving any software-development effort."

Do you agree with that?

If I create a method like DWORD.PRG in ClassA, when another part of the application needs that DWORD method, I must do more work to get at that code. I first have to remember the class it is contained in, then I either instantiate that class or copy it from the imagelist to ClassB. That slows construction, it slows execution. If it is left separate I may have to find it, but that is already simplified by its name. If it is copied in 10 classes, fixing it 10 times is more construction!

Unit-testing and integration-testing is not construction.

From a diagram in Code Complete, corrective maintenance is less significant than construction and nowhere do I see anything about portability, which I raised in another thread.