"I assure readers that this kind of problem is only faced by beginners" I disagree. I've even brought this up before in passing on HN: https://news.ycombinat

"I assure readers that this kind of problem is only faced by beginners" I disagree. I've even brought this up before in passing on HN: https://news.ycombinator.com/item?id=5639846 https://news.ycombinator.com/item?id=5639846 I've written many thousands of lines of Go code and have been using the language for more than a year and I still think the gist of the author's argument is a valid pain point when it comes to Go documentation. I'm now very familiar with the standard Go library, so the problem doesn't impact me as much as it used to, but I do find auto-generated Go documentation for new libraries I haven't yet used to be much harder to get a quick mental overview of than code autogenerated from other languages I've programmed in (including languages which are OO, functional or procedural). Go is still my favorite language to program in, but I think there is a valid issue here (one that can be fixed with improved tooling)