Golang News

Go best practices, six years in

Sun, 01 May 2016 18:14:00 +0000

20 points posted by kenny

Peter Bourgon · Go for Industrial Programming

Sun, 03 Jun 2018 07:08:00 +0000

Peter Bourgon has a web site, and this is that web site. 19 points posted by kenny

Logging vs instrumentation

Fri, 15 Jul 2016 07:20:00 +0000

16 points posted by Tim Donell

OK log - distributed and coördination-free log management

Tue, 17 Jan 2017 14:10:00 +0000

OK Log is a distributed and coördination-free log management system for big ol’ clusters. Peter Bourgon built it from first principles, to teach himself the gory details of shuffling logs around. This is the story of the prototype.

12 points posted by kenny

Logging v Instrumentation

Mon, 08 Feb 2016 01:16:00 +0000

9 points posted by andythomas

A theory of modern go

Fri, 09 Jun 2017 13:14:00 +0000

8 points posted by kenny

Semantic Import Versioning is unsound

Mon, 14 Sep 2020 17:56:00 +0000

6 points posted by kenny

Metrics, tracing and logging

Tue, 21 Feb 2017 19:39:00 +0000

6 points posted by gopher

Context - a user's guide

Thu, 14 Jul 2016 15:48:00 +0000

6 points posted by kenny

Go kit: Go in the modern enterprise

Mon, 28 Sep 2015 23:19:00 +0000

6 points posted by gopher

Dont use build tags for integration tests

Fri, 02 Apr 2021 12:16:00 +0000

4 points posted by tomf

Programming with errors

Wed, 18 Sep 2019 22:14:00 +0000

Go 1.13 introduces an enhanced package errors (née xerrors) which roughly standardizes programming with errors. Personally, I find the API confusing. This is a quick reference for how to use it effectively. 4 points posted by kenny

A case for microservices

Tue, 17 Nov 2015 13:13:00 +0000

4 points posted by kenny

Go best practices in production

Wed, 07 Oct 2015 12:19:00 +0000

4 points posted by kenny

Peter Bourgon · A response about dep and vgo

Fri, 27 Jul 2018 18:50:00 +0000

Russ Cox did a tweetstorm about his perspective on the dep/vgo/modules story. It’s not a lot of fun to re-litigate histories, but there are some subtle and important problems in this narrative, and it’s important to me that I have something on the record that objects to those problems as I see them. I think it’s important because Go’s leadership spends a lot of time and energy on promoting the notion of a community culture, and I think this incident, in all of its messy and protracted complexity, stands as pretty compelling evidence that they haven’t figured out the right protocols for that, yet. It’s important that there’s an accurate history on the record, so that future endeavors can improve on the mistakes of the past. 3 points posted by tomf