Every Dev Should Know This! (Software Architecture Ep. 4: Coupling Metrics)

Описание: Most software developers have heard of "DRY" (don't repeat yourself) and follow it carefully. You may be surprised to learn, however, that bad coupling is often more painful than repetition, and most developers don't know how to measure it!

Learn how you can measure coupling by counting the afferent (incoming) and efferent (outgoing) connections to a module, or by considering the instability (% efferent connections) and abstractness (% abstract classes) of your module.

We finally define the Distance from the Main Sequence as D = abs(Abstractness + Instability - 1) and show how it can tip a module into the Zone of Uselessness or the Zone of Pain, and how minimizing D results in a more ideally coupled module.

I've also shared a real world example of Coupling Metrics in action below.

↓ ↓ Links below ↓ ↓

📚 Learning Material:
➡️ Fundamentals of Software Architecture: https://amzn.to/3VwYMN7
➡️ More on Coupling Metrics: https://101.jqassistant.org/calculate...
➡️ Real World Example (on the neo4j codebase):   / abstractness-vs-instability-neo4j-case-study  

⭐️ My Links:
➡️ LinkedIn:   / miles-aron  
➡️ Arcanium Ventures: https://www.arcanium.vc

🎬 Chapters:
00:00 - Intro
00:42 - Efferent vs Afferent Coupling
01:38 - Abstractness
03:09 - Instability
04:27 - Distance from the Main Sequence
06:47 - Outro

#software #softwarearchitecture #softwareengineering #softwaredevelopment #tech