How-to fix tightly coupled Go code

Have you ever added a new feature only to have another one break?  After fixing the break, something else breaks, like some kind of bug whack-a-mole? Have you ever spent hours debugging a broken test only to find the issue lurking in another, supposedly unrelated package? These issues are caused by code being tightly coupled. […]