Search code examples
separation-of-concernsdecouplingcoupling

Is "coupling" related only to code, or can the term be applied to software components and architecture?


For example, when discussing a build or deploy process, and making sure it is independent of the IDE. Is this "coupling", or is that considered Separation of Concerns, or something completely different? The general concept is to introduce the least number of variables into a process or architecture, so that when a failure occurs, the difficulty in identifying the possible points of failure are reduced significantly. Is there another definition for that?


Solution

  • Something completely different.

    Coupling is code.

    Independent tools are just independent tools.

    Microsoft has lead me to believe that independent tools are a bad idea. They tell me that one vendor's integrated tool suite is a good thing.