Took me 17 years of struggle, but I can finally explain cohesion in software design. I dropped the Cohesion chapter of the #TidyFirst book yesterday. I'll summarize here. tidyfirst.substack.com/p/cohesion #payWall
An element is cohesive if its sub-elements are coupled. A file is cohesive if all its functions have to be changed at the same time.
"Isn't that bad that they all have to be changed at the same time?"
Compared to what? Having those functions in different files is worse. It's easy to miss one.
Compared to what? Having those functions in different files is worse. It's easy to miss one.
Also, what if there are also a bunch of functions that don't have to be changed. Now we have to peruse those to make sure they aren't affected.
Cohesion:
* Things that have to change together *are* together.
* Things that don't have to change together are apart. Where? That's for you to figure out, designer. But likely with the things that have to change at the same time.
* Things that have to change together *are* together.
* Things that don't have to change together are apart. Where? That's for you to figure out, designer. But likely with the things that have to change at the same time.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
