in reply to So much interconnectedness - good or bad?

connectedness is good - it means you're reusing code. interconnectedness is bad - it means that you have tight coupling.

The problem is that you have circular dependencies. The ideal situation is that when you look at your dependencies in a picture (circles showing the modules, arrows showing the dependencies), you should never be able to start in one place, follow the arrows and end up where you started. If you can, you need to refactor.

Already, you can see that you have cycles between C & D, and A & D. It sounds like you need to revisit which functions live in which modules. It may be that you need to refactor the functions themselves. Maybe a function is doing too many things at once. :-)

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

  • Comment on Re: So much interconnectedness - good or bad?

Replies are listed 'Best First'.
Re^2: So much interconnectedness - good or bad?
by kiat (Vicar) on Dec 17, 2004 at 14:51 UTC
    Thanks, dragonchild!

    Good to know it's not all that bad.

    I plunged into the coding without formal planning. As I add more and more lines of code, the complexity of the inter-connections grows.

    It's time I do the circles and arrows thing.