It's an interesting post and something I can see being true to an extent, but I'd like to put forward an alternative from my own experience.
I came to Go as an extremely inexperienced programmer - a couple of years with Perl and a childhood with C64 basic/6502/Z80 and virtually no formal CS background (one half year unit in first year undergrad). When I started using Go it had only been open sourced for a year and a half. I found the support for people starting to use Go to be outstanding even when questions were only tangentially related to Go (generic algorithmic problems were happily(?) helped with). In part it seems this was due to decisions by the Go core developers to help foster a helpful and welcoming environment (rsc has discussed the motivations for this in the past). Maybe that "fresh scene" has diminished a little, but it doesn't really seem so to me. Dan On Tue, 2016-07-19 at 08:16 -0700, Matt Aimonetti wrote: > I just wanted to point out a post I published today talking about the fact > that we are often leaving new / less experienced Go developers high and dry: > https://medium.com/@mattetti/go-is-for-everyone-b4f84be04c43 > > I'd love to see what you all in mind to help new or junior developers. > Maybe share some of the pain points you've experienced or seen (for > instance setting up the Go path, finding resources to get started etc...) > I'm thinking about a bunch of very short posts on basic topics and maybe a > real beginner tour of Go. We are going to do a beginner night next month at > our LA/Santa Monica Go meetup and hopefully better understand what the > current pain points/blockers are. > > What do you think? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
