But I haven't used a debugger in at least ten years. Production Go for the past few.
I debug with good log messages.
Of course, not everyone's problems are exactly like mine, so I will believe you if you say it's necessary for your situation.
I think that this point about team conversations is incredibly important. Apart from Ruby, Go is the only language that I know where the technical conversations seem to consistently focus on the problem at hand, rather than coding concerns like the finer points of language features. The company that I work for does both Ruby and C#, and the difference in the conversations around the two is very noticeable.
You can also try https://github.com/derekparker/delve
https://github.com/Microsoft/vscode-go/wiki/Debugging-Go-cod...
I've used it for debugging unit tests. Very handy.