In the most elementary guidance on application and system design comes the rule "favor low coupling and high cohesion". This idea of "good fences makes good neighbors" makes perfect sense conceptually, but how do we actually put this idea in practice? How do we know we have good coupling and good cohesion versus bad? And how do we apply these concepts practically at varying levels of design?

It may seem the end goal is zero coupling, but this makes it impossible for objects or systems to function without any sort of collaboration. How do we break through this paradox?

In this session, we'll look at the varying types of coupling we can find in our code, large and small. We'll also look at defining patterns of encapsulation from classes up to systems. Finally, we'll tackle ways of exposing capabilities between boundaries to ensure our systems stay low coupled and highly cohesive without sacrificing developer productivity or user experience.