Packages as Layers, Not Groups: gobeyond.dev/packages-as-la… (Looking at your packages as layers is a step toward a hexagonal architecture and can clean up your code structure significantly.)

@golangweekly This is why OSI model has strict segregation between layers :-)

@golangweekly Shameless related promotion present.gon.cat/uservices.slid…

@golangweekly A series of blog posts with a related perspective, for F#. F#'s namespacing and Go's packaging are quite different to use, but similar constraint on avoiding circular dependencies and breaking projects up into layers. fsharpforfunandprofit.com/posts/cyclic-d…

@golangweekly good article，good idea