You’re not as loosely coupled as you think!
You’re not as loosely coupled as you think!
When you hear tight coupling or being loosely coupled, what does that even mean? There are many aspects to coupling to consider.
-
All code today is coupled to complex ecosystems which may thrive or perish later. There are no good solutions which can be given out as generic advice.
And even specific solutions to any tech stack can be hit or miss. Time kills all projects unless they are run in a frozen environment which itself keeps up with the times, constantly
-
Cool so this article calls out various types of coupling and offers no strategies for managing it.
Waste of time.
-
The "solution" is buy their product.
Sponsor: Do you build complex software systems? See how [redacted] makes it easier to design, build, and manage software systems that use message queues to achieve loose coupling. Get started for free [link redacted]
This article is an ad.
-
Reminds me of one site that said I shouldn't use 'git secret' because reasons. I've spent quite some time to find what do they propose to use instead (that wasn't as straightforward as in this article), turns out they provide a 'solution' that includes their partners' system to manage secrets. Another bullshit, in other words
-
-
-
Me and my code are in a situationship
-
I'm not loosely coupled at all, sir, I am married!