golang

maintains MUST READ articles

Quick Tutorial

• A Taste of Go
• Golang Cheat Sheet
• Go for Java Programmers
• Golang Naming Convention

Language Design

When reading code, it should be clear what the program will do.
When writing code, it should be clear how to make the program do what you want.

• Rob Pike: Simplicity is Complicated

Leading edge language features don't usually address what you really want.
Golang is designed for large applications, large teams and large dependencies.

• Rob Pike: Go at Google Article, Video

• Golang FAQ: Design

• Golang FAQ: Types

• Campoy: Functional Go?

Tools

• Go Tooling in Action
• Debugging Go programs with Delve Article, Video

Idiomatic Go

• Rob Pike: Go Proverb Page, Video
• Campoy: Understanding nil
• Twelve Go Best Practices: Slide, Video
• Go best practices, six years in: Article, Video

Concurrency

Concurrency is about structure, while Paralleism is about execution

• Rob Pike: Concurrency is not Parallelism Slide, Video
• Go Concurrency Patterns
• Curious Channels
• Complex Concurrency Patterns With Go
• Advanced Go Concurrency Patterns

Error Handling

Error values in Go aren’t special, they are just values like any other, and so you have the entire language at your disposal.

• Go Blog: Defer, Panic, and Recover
• Go Blog: Error Handling and Go
• Go Blog: Errors are Values
• Dave Cheney: Don't just check errors, handle them gracefully Article, Video

Go solves the exception problem by not having exceptions.
... The decision to not include exceptions in Go is an example of its simplicity and orthogonality. Using multiple return values and a simple convention, Go solves the problem of letting programmers know when things have gone wrong and reserves panic for the truly exceptional.

• Dave Cheney: Why Go gets exceptions right
• Dave Cheney: Inspecting errors
• Dave Cheney: Error handling vs. exceptions redux
• Dave Cheney: Errors and Exceptions, redux

Knowing the difference between which errors to ignore and which to check is why we’re paid as professionals.

• Dave Cheney: Constant errors
• Dave Cheney: Stack traces and the errors package

Interface

If C++ and Java are about type hierarchies and the taxonomy of types, Go is about composition

Q. Hey gophers, what was the best/worst moment of your experienes lenaring golang?
A. The worst was interface, but the best was also interface

• Stackoverflow: What's the mearning of interface{} ?
• How to use interfaces in Go

Struct

• Dave Cheney: Struct composition with Go
• Dave Cheney: The empty struct

Pointer

• Dave Cheney: Pointers in Go
• Things I Wish Someone Had Told Me About Go
• Dave Cheney: Go has both make and new functions, what gives?
• Dave Cheney: Should methods be declared on T or *T

Map, Slice

• Go Blog: Map in Action
• Go Blog: Slices Usage and Internals

Logging

• The Hunt for a Logger Interface
• Logging v. instrumentation
• Dave Cheney: Let’s talk about logging

Encoding, JSON

• JSON, interface, and go generate