liveBook · Manning

Coupling

As explained in Build High Value Software Systems

A dependency relationship in which one software component relies on another component's structure, behavior, or availability.

Coupling is a dependency between components that can make changes or deletions costly. A caching experiment might require edits across more than seven files, or just a one-line change and removal of one file. section 4.2.1

Listing 4.5 Coupling impacting maintainability
// Hard to delete: implicitly depends on global state
function process() {
  const config = globalConfig.processingRules; // Where did this come from?
}
 
// Easy to delete: explicitly declared
function process(config: ProcessingRules) {
  // Clear what this needs
}

Compare an implicit dependency on global configuration with a function that declares its configuration parameter. section 4.2.1

Let expected lifespan guide design. Keep short-lived experiments clear, local, and easy to remove. For capabilities expected to endure, favor explicit interfaces, managed dependencies, tested behavior, and documentation. section 4.2.1

In code review, treat hard-to-remove coupling as a possible merge blocker; check whether code is isolated rather than scattered across unrelated files. AI-assisted workflows can also become tightly coupled to a model’s behavior: keep the spec stable and adjust reusable prompts or templates when the model changes. section 4.4.3 section 14.5

How Build High Value Software Systems covers it

How deep it goes
Contrasts implicit global-state dependence with an explicit parameter and links scattered behavior to deletion effort, without formal coupling metrics.
Examples
Uses a caching-layer deletion comparison, a function dependent on global configuration, and prompts tied to model behavior.
What you can do after
Diagnose deletion risk by tracing implicit dependencies and checking whether behavior is isolated or scattered across files.
How it connects
Connects coupling to code deletability, maintainability, code review, global state, and AI workflow brittleness.

Also explained in

Compare how 22 books explain coupling →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.