To be honest, the best method is to find good Go libraries and do some code reading. Not every project will be using best practices, even those created by prominent Go developers, but if you read through several libraries, you'll pick things up by osmosis.
The name of the repo is really and intentionally misleading. rsc filled an issue there to point this out, but the repo maintainer just disabled issues altogether so now no one can see it.
Even when it would not have such parasitic name, many seasoned Go programmers, me included, consider the self-proclaimed "Standard Go project Layout" as the opposite of what is good and advisable.
Unfortunately, the name just works, so it is being recommended all over the Internet since its inception.
2 comments
[ 2.2 ms ] story [ 19.0 ms ] threadThat said, https://go.dev/doc/modules/layout and https://github.com/golang-standards/project-layout may help.
The name of the repo is really and intentionally misleading. rsc filled an issue there to point this out, but the repo maintainer just disabled issues altogether so now no one can see it.
Even when it would not have such parasitic name, many seasoned Go programmers, me included, consider the self-proclaimed "Standard Go project Layout" as the opposite of what is good and advisable.
Unfortunately, the name just works, so it is being recommended all over the Internet since its inception.