Add section "Connascence"

Author: webpro

README.md

@@ -29,6 +29,7 @@ have any feedback or suggestions for improvement!
 
 ### Inter-Module/Class
 
+- [Connascence](#connascence)
 - [Minimise Coupling](#minimise-coupling)
 - [Law of Demeter](#law-of-demeter)
 - [Composition Over Inheritance](#composition-over-inheritance)
@@ -259,6 +260,30 @@ Resources
 
 - [Opportunistic Refactoring](https://martinfowler.com/bliki/OpportunisticRefactoring.html)
 
+## Connascence
+
+Connascence is a software quality metric that describes different levels and
+dimensions of coupling. Two components are connascent if a change in one would
+require a change in the other as well. Lower connascence means higher code
+quality.
+
+Why
+
+- Reducing connascence will reduce the cost of change for a software system.
+- Arguably one of the most important benefits of connascence is that it gives
+  developers a vocabulary to talk about different types of coupling.
+
+How
+
+- Each instance of connascence in a codebase is considered on 3 separate axes:
+  strength, degree and locality.
+- It provides a system for comparing different types of dependency.
+
+Resources
+
+- [Connascence (connascence.io)](https://connascence.io)
+- [Connascence (wikipedia.org)](https://en.wikipedia.org/wiki/Connascence)
+
 ## Minimise Coupling
 
 Coupling between modules or components is their degree of mutual