There are a lot of problems with this approach and a few errors in the post, but I'm just going to highlight the most significant one: > If the project uses CI

There are a lot of problems with this approach and a few errors in the post, but I'm just going to highlight the most significant one: > If the project uses CI/CD or just for consistency, it is good to keep the list of dependencies used in packages. This is done by the “deps” task, which should get all the necessary dependencies by “go get” command. This is a very strong anti-pattern. Everyone should be using a dedicated version management tool (ideally dep[0], but there are others), which handles this seamlessly and behind the scenes. Introducing another place where dependencies are tracked and can be installed is a recipe for problems down the line. [0] https://github.com/golang/dep/ https://github.com/golang/dep/