ongoing by Tim Bray, podcast version

A friend of mine pinged me online, said “Hey, remember that thing we were talking about doing a couple years ago? I still have one of the domain names, gonna let it go unless you want it.”...

When I introduced Quamina, I described the core trick: You prepare an arbitrary JSON blob for automaton-based matching by “Flattening” it into a list of name/value pairs, then sorting them in name order. Today, a closer look at how you work with the flattened data...

My coding time this year has been invested in Quamina, an event-filtering library implemented in Go. Just in the last couple of weeks I spotted an opportunity to bring Go’s shiny new generics to bear, and not just anywhere, but for a central data structure. I got good results, but the process was sort of painful; I kept trying things that looked like they ought to work but didn’t. I’m sharing this tour through that experience because I’m a reasonably competent programmer with mainstream tastes and if I hit these bumps in the road others probably will too...

No parent will name a favorite among their children. But I do have one among my brainchildren, my software contributions over the decades: The event-streaming code I helped build at AWS. After rage-quitting I missed it so much that over the last few months, I wrote a library (in Go) called Quamina (GitHub) that does some of the same things. This is about that...

Once again, a selection of long-form pieces for those who (unlike me) have jobs and won’t have time for all of, but might benefit from ingesting one or two. This month we have lots of musical offerings, along with politics, advice on how to walk, and 5G...

The odometer on my e-bike clicked over to 4K and, rather than a general-purpose “e-bikes are great” rave, I thought I’d assemble a few concrete arguments for them, suitable for re-use with friends and loved ones in the (likely) case that you’re already convinced. With pictures...

We live in a world of things that have Product Managers and Design Teams and Documentation Architecture and often vast ambition. And yet, so many of them are so bad. And worse, some which are good then become bad for no good reason. There is a particular joy in a product that just does what you need done, in about the way you expect or (thrillingly) better, and isn’t hard to figure out, and doesn’t change unnecessarily. Here are three to learn from...

Welcome to another Long Links, selected pointers to long-form pieces that have added value to my semi-retired days and one or two of which might reward you if you make time for them. A few of this month’s pieces aren’t free; it’s a bitter fact that the truth is paywalled but the lies are free. Sorry...

When I was working at AWS, around 2017 we started getting excited pitches from companies who wanted to be part of the 5G build-out, saying that obviously there’d be lots of opportunities for public-cloud providers. But I never walked away convinced. Either I didn’t believe the supposed customers really needed what 5G offered, or I didn’t believe the opportunity was anywhere near big enough to justify the trillion-dollar build-out investment. Six years later, I still don’t. This is a report on a little online survey I ran, looking for actual real-world 5G impact to see if I was wrong...

To misquote William Gibson: “The past is still here with us, just unevenly distributed.” I have a story to tell that stars Sergei Rachmaninoff and me. It starts just before 1900 in Moscow. My part ends around 1972 in the mountains of Lebanon, looking down over Beirut and the blue Mediterranean. It doesn’t have to do with computers and nothing in it matters to anyone living except me, but maybe you’ll enjoy a faintly exotic musical echo from a long time ago a long way away...