You can ask 100 gophers. And obtain 100 different workflows ;) I like to separate design and code, from build and test, from deploy and monitoring. And I like

You can ask 100 gophers. And obtain 100 different workflows ;) I like to separate design and code, from build and test, from deploy and monitoring. And I like change. And experimenting with new techniques. dep is definitely next, as well as prometheus. The things that determine what tools you use are often external to language design itself. How your remote team handles its gitflow. Whether people prefer vim on a remote dev instance or Atom locally with github integration. Are you targeting app engine or container engine. Regardless of the heterogeneity, having a canonical $GOROOT source tree and deploying binaries makes things much more flexible. I'll just point to one recent discovery that is helping a lot at the moment and may be useful to other people: godoc for static analysis https://golang.org/lib/godoc/analysis/help.html https://golang.org/lib/godoc/analysis/help.html