Careful with io.TeeReader and json.Decoder

Some time ago, I was investigating very strange bug in our codebase: http: ContentLength=513 with Body length 512 It was inside our Go reverse proxy, and what was very suspicious was the exact 1 byte discrepancy. My suspicion was on gzip middleware, which is often the cause when you forget to set request.ContentLength after compressing the payload. However it turns out it was not the case. Do you see anything problematic here?

Jon Bodner - Closures are the Generics of Go

Steve Francia - 7 common mistakes in Go and when to avoid them

Dave Cheney - Constant Time

Kavya Joshi - Understanding Channels

Great talk about internals of Go channels.

Peter Bourgon - Go + Microservices = Go Kit

Dave Cheney - Seven ways to Profile Go Applications

Dave Cheney - SOLID Go Design

Rob Pike - Go Proverbs

Rob Pike - 'Concurrency Is Not Parallelism'