decoupling

Even within maths, rigorous proofs require decoupling of the abstract proposition (what you prove) from reality (your assumptions).

Design patterns allow the code to be written in a reusable manner by decoupling some responsibilities.

We're open to decoupling 'upvote' from 'save', but what would the interface for 'save' be?

Also, decoupling the € from the $, or even the ¥ is naive.

Now when it comes to UIs I favor decoupling at the expense of a little code duplication.

I'd say they are vaguely related through decoupling the traditional structure of computations through reified objects.

Personally I would love to see the decoupling of TypeScript's type checker from its transpiler.

I'd love to see this evolve into something that uses hardware and software decoupling to enable more effective and deep experiments.

It's the knee jerk reflex of decoupling everything, to the point that you have 80% configuration/wiring/setup vs 20% of code that actually does something useful.

And most language implementors sufficiently well read to know how to apply GC, but a little ignorant of providing space for a complete decoupling of GC.

You gain a bit of flexibility by decoupling initialization into a function, but you also gain a bit of verbosity and lose a little bit of modularity.

I still quote this in internal meetings, about decoupling our business components.

For the curious, California achieves this by a regulatory measure called "decoupling": a utility's profits are not connected to how much raw energy it sells.

Decoupling does not reduce the overall bill for ratepayers.

Decoupling slow memory reads from the op that uses their values gives the CPU more flexibility in scheduling to try and hide the latency of memory ops.