I was hoping this article would have more substantive advice for new Go developers.  It seemed to mostly have very general advice that applies to most other languages like: &quot;Don&#x27;t try and write language X in language Y.  Keep complexity down by not over using complex language features.&quot;<p>I&#x27;m writing my current hobby project, a podcast fetcher, as my first project in Go.<p>The project has been going generally well but there have been a few annoyances so far:<p>*  Why are you not able to easily version git dependencies?  Go&#x27;s solution to this problem is to tell you to create an entirely new git repository for each major version. Really?  If they didn&#x27;t want to go full blown dependency versioning with something like CocoaPods, they could at least let you specify a git branch or tag.<p>*  The db.Sql abstraction does not support multiple result sets.  Therefore database drivers, like the popular mysql driver, don&#x27;t support multiple result sets.  This really limits the kinds of stored procedures you can call.<p>* The debugger support is bad.  I have to fall back to using print statements for most of my debugging.