I’ve renamed this newsletter.
Until today the name of this newsletter was “Explicit Coupling”. Of course, I intended that to refer to my take on how to decide what “good” code looks like: all of this module’s coupling with the rest of the world is explicitly documented locally, here, in the source code of this module itself. All of the coupling is Explicit.
But there’s a NSFW interpretation of the phrase Explicit Coupling too. Some people found that offensive, and some found it sufficiently risqué that it became a distraction. So that name had to go.
And in fact, since I explored what the Table of Contents might look like If This Were a Book, I’ve felt that I probably need to cover the whole process of refactoring — possibly most of TDD too — if I’m going to be able to describe my take on coupling in a way that addresses every angle. So generalising the name of this publication to Habitable Code feels like a good fit with where I now realise I’m heading.
Onwards and upwards.
Thanks for being a subscriber!