So many times dev teams wish they had more logging, but so very often I’ve used the *absence* of logs to diagnose an issue. Tracing through and asking “how can no logs be produced from this method” is just as effective as “how was this log line produced”. Read between the (log) lines.

Guy at brewery: “What’s on your shirt?”

Me: “Oh, this is the Go gopher, from the Go programming language. I just got back from…”

Guy: “oh, I thought it was a roast beef sandwich on a surfboard”

The shirt:

Another #GopherCon done! It was so excellent to see many old friends, make some new ones, and learn so many new things along the way too! Looking forward to next year!

TinyGoOS: should the proper pronunciation be “Tiny Goose” #GopherCon

Excited for #GopherCon Day 2!

@gdey.me great talk! Been a user of this platform for a few months (a year maybe?)—now I’m excited to go build something with it!

Time to learn how this AT Proto thing I’m using actually works! #GopherCon

One underrated aspect of this protobuf talk is the configurability of a safe and unsafe path in the library. I like that it makes it possible to optimize with unsafe, but allow users to choose whether they want unsafe in their codebase. #GopherCon

I really can’t wait to check out github.com/google/capsl... #GopherCon

Loving this talk on supply chain attacks at #GopherCon . The original “Reflections on Trusting Trust” rings true even today.

@swtch.com Great to see you last night! Hope you enjoyed the show as much as we did!

Periodic reminder that the correct type for any field labeled “Port” is “uint16”, not “string”. If you need a string, coerce the stricter type (uint16) to the less strict one (string).

Today I framed our poster from the very special Futures 20th Anniversary show we went to in Phoenix back in October—it seemed appropriate on 12.23 😅 It’ll be hanging in my music nook with my piano and guitar.

Obligatory first Bluesky post :) It’s nice to actually see activity here instead of the ghost-town cesspool of Twitter.