From ba7443e4d7d49c156c126491060ecdbd59c6bcac Mon Sep 17 00:00:00 2001 From: Quentin Date: Wed, 8 Jan 2025 21:52:49 +0100 Subject: [PATCH] More specific word: very good=>great --- documentation/hexagonal-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/hexagonal-architecture.md b/documentation/hexagonal-architecture.md index 59642ff412..edfec0d8a6 100644 --- a/documentation/hexagonal-architecture.md +++ b/documentation/hexagonal-architecture.md @@ -45,7 +45,7 @@ In software development if you want to go faster (like really faster) you'll hav Let's be honest here: hexagonal architecture won't help for the fastest feedback loops which are pair feedback in [pair](https://en.wikipedia.org/wiki/Pair_programming) or [mob programming](https://en.wikipedia.org/wiki/Mob_programming). -BUT, just after that comes compilation and, for that, hexagonal architecture will help! Thanks to the very good Separation Of Concern you'll be able to build modules (packages in Java) with a very high cohesion and very low coupling. That means, most classes in the infrastructure modules will never get out of there hence allowing compilation time feedbacks. +BUT, just after that comes compilation and, for that, hexagonal architecture will help! Thanks to the great Separation Of Concern you'll be able to build modules (packages in Java) with a very high cohesion and very low coupling. That means, most classes in the infrastructure modules will never get out of there hence allowing compilation time feedbacks. There is another **AWESOME** compilation time feedback coming not directly from the architecture but from a practice often used in that architecture: Types Driven Development. The idea is pretty simple: create a dedicated type for each business concept. Example: