Don't Panic

In the before times, I typically used a small, curated handful of git worktrees.

Whenever possible, I leave my webcam off during internet meetings.

I’ve played nearly every NYT Connections.

When writing a service, it’s very easy to accidentally forget to check permissions or ownership of an object.

Exponential backoff with jitter is de rigeur for making service calls.

Lots of people don’t want to read about AI.

I have started a podcast, Significant Bits.

I didn’t sit down this morning planning to write a grouchy blog post about Hugo.

This post was originally tweets but then things happened, and it needed a new linkable home.

Go templates (text/template, html/template) accept a single argument to render.

Linus’s Famous Law: “Given enough eyeballs, all bugs are shallow.”

Around this time in the Go release cycle, the Go team asks people to test Go betas and release candidates.

Lookup tables are powerful micro-optimization tools, because they implement arbitrary transformations in cheap constant time.

A small thing of which I am irrationally proud: I was the proximate cause for the addition of a sentence to the RISC-V ISA spec.

This is the first blog post I’ve written that isn’t about Go, and it’s pretty weedy.

It’s easy to forget to call go generate when you need to.

As of Go 1.15, the Go runtime’s memory allocator doesn’t always allocate exactly the number of bytes required for an object.

If you are desperate for 6% smaller Go binaries, this blog post is for you.

This blog post covers string interning in Go.

My favorite new API in Go 1.13 is testing.B.ReportMetric.

The Go 1 compatibility promise was designed to ensure “that Go 1 will be a firm foundation for the development of Go and its ecosystem.”

Go program execution doesn’t start at func main.

This post is about some new compiler optimizations scheduled for Go 1.9, but I want to start with logging.

If you work on a short-lived, allocation heavy program and care about a tiny (maybe 0.5%) performance improvement, this post is for you.

This post is about a little-known way to make compile-time assertions in Go.

I’m going to try this blogging thing again.