Suitable for work

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é...