How We Went from 30 Servers to 2: Go
> "We also weren't sure if we would be able hire top talent if we chose Go, but we soon found out that we could get top talent because we chose Go."I feel[1] that a smart/talented C/C++/anything developer can go from someone who has never seen or heard of golang to a proficient and productive Go developer in a matter of a few weeks, maybe even _days_, if not less.That's how long it takes to go through the following materials (and fav some for later reference) and play with the language a bit.http://golang.org/ref/spechttp://www.youtube.com/watch?v=ytEkHepK08chttp://commandcenter.blogspot.com.au/2012/06/less-is-exponen...http://tour.golang.org/http://golang.org/doc/installhttp://www.youtube.com/watch?v=XCsL89YtqCshttp://golang.org/doc/code.htmlhttp://golang.org/doc/effective_go.htmlhttp://golang.org/pkg/ - use as referencehttp://www.youtube.com/watch?v=f6kdp27TYZshttp://talks.golang.org/2012/splash.articlehttps://gobyexample.com/http://golang-examples.tumblr.com/And a some more similar things that you can mostly get to from golang.org site. The beauty of how concise the language and even its website are, is that you can literally just go through everything there one thing after another.[1] This is my personal opinion based on playing with go the last few weeks/months. I'd love to verify this theory. It's not yet the primary language in which I do things in (I use C++11 atm), but for all my side tasks[2] it proved to be indispensable. And I found it very easy to pick up. I can't wait until I start doing all my work in Go, that will be a true test of its productivity efficiency.[2] https://gist.github.com/shurcooL