It’s been about a year since my “gopiphany” post where I described how I’d fallen in love with go.
A year later, and the series of blog posts I planned on writing didn’t materialize on the timeline I thought they would then, but I’m still very excited about go.
I did sketch out a lot of posts, and I went to conferences, and it turns out that I’m not the only person to find that there is a significant gap between what the go tutorials cover and what you need to be an effective programmer in go. For instance, at GopherCon 2016 Katrina Owen gave a talk called Mind The Gap. I very nearly helped out with that during the hack day but of course ended up playing instead with a go unikernel project, because of course I did.
Another benefit of my inability to blog for a year solid, is that in the meantime I’ve been really using the results of my initial research into the functional areas I felt I was lacking. I might not have found the best approaches, but at least I’ve got some real world experience (if a San Francisco start-up counts as “real world”) in a handful of the libraries which I felt were the best for my needs at the time.
I recently used a commitment device, which was to sign up for a slot in an “advent calendar” of golang posts. And to keep things safe, I have chosen as a topic a library which I’ve been making extensive use of, go’s context library. The title has three applications of that library, so as a warm-up to the single concise posts, I’ll be writing three more in depth posts about each application.
So, the good things come to those who wait. Instead of a series of posts from a go newbie about what libraries are in a particular problem space you could probably google yourself and filled with opinions you don’t care for yet, you’ll be getting high quality experienced writings. I hope you enjoy, subscribe, comment or at least find it useful.
In the meantime, here’s another meta post using a lot of future tense :-)