Austin Phillips

The one where a big grouped inbox stops making you wait a full minute to open an email. Turns out asking SQLite to rescan the whole folder once per message is bad for business. Who knew. (We should have.)

Faster

• Grouped inboxes are fast again. Picking the newest message in each thread used to walk the entire folder once per message. That's quadratic, and on a 15k-message inbox it took over a minute, and every other read waited in line behind it. So after launch you got a blank list and a nice long think. One new index later, the same query takes 68 s 20 ms. A test now pins the query plan so it can't quietly come back.

• Inline images no longer freeze the window while a sync is running. They're now loaded off the UI thread, where they should have been all along.

New

I ve tried a few AI powered coding editors and the workflow feels quite different from using a traditional IDE. The suggestions are useful, but sometimes I prefer the predictability of a normal setup. For web development, which approach works better for you and why?

I've been working on internal documentation recently, and one thing that keeps coming up is that creating the documentation isn't necessarily the difficult part keeping it accurate is.

A process gets documented, someone changes a few steps a month later, and eventually the original guide no longer matches what people actually do.

I've seen teams handle this in very different ways:

• Assign an owner to each document

• Review SOPs every few months

• Update documentation whenever a process changes

• Keep a video walkthrough alongside the written instructions

• Just fix the documentation when someone notices it's wrong