I'm @brandur, a software engineer, and dabbler in writing and photography.
This site is where I publish words and photos. The section that's most updated most often is atoms, small multimedia particles reminiscent of a Twitter feed. I update my now page monthly according to what I'm working on and thinking about. I publish a newsletter as often as I can.
Once in a while, I write longer form articles on technical subjects like APIs, Go, or Postgres:
Using a two-phase data load and render pattern to prevent N+1 queries in a generalized way. Especially useful in Go, but applicable in any language.
Maximizing Postgres connection economy by using a single connection per program to receive and distribute all listen/notify notifications.
Using Go’s DisallowUnknownFields
option to improve an API’s integration experience by making paramter naming mistakes faster to resolve.
I put short stream of consciousness thoughts into tiny posts called fragments:
As of Go 1.21, Go fetches toolchains automatically, and it’s easy to not be running the version that you thought you were running.
I broke my promise never to give FromSoftware money again, and it was okay.
Quick thoughts on whether sqlc is still the direction for Go projects now that we’ve been using it for three years.
I write a newsletter about the philosophy of software called Nanoglyph:
Upgrading to Postgres 16, NULLS NOT DISTINCT
, the iPhone 15 + its new battery option, and San Francisco under the shadow of APEC.
Attending Rails World in Amsterdam (finally a conference to get excited about). Solid Cache and Solid Queue. CTEs in Rails 7.1.