Loose vs Tight Coupling

In software engineering, we sometimes refer to code as being loose or tightly coupled. In this video I cover the details of what software engineers mean by both coupling and cohesion as well as dive into a specific example so the terms aren’t just abstract.

Finally, I risk going to engineering hell by suggesting you don’t always need to make your code loosely coupled! Engineering is about tradeoffs and I cover what tradeoffs I see as well as the questions I like to ask myself when deciding how loosely coupled to make my code.

0:15 - Coupling
0:43 - Cohesion
1:07 - Benefits of Loose Coupling
1:37 - Example
3:25 - Tradeoffs
4:35 - Questions to help measure tradeoffs