When the Free Raisins had been playing for ~3.5 years I put together a set of charts showing how booking had worked for us. Since it's now been another 3.5y I thought I'd make some updated charts.
Here's a chart showing when we booked each gig, and how long from then until we played it:
(While this is accurate for bookings through today it doesn't show the full picture for gigs because we might still get booked for something on shorter notice.)
I also made a chart showing how often we asked for gigs (blue), vs were asked (red), vs put together a tour (green):
One big change is that since we now live on two coasts and in three states we can pretty much only take gigs if they're willing to fly us, which mostly just means dance weekends. We also haven't organized a substantial tour since the summer 2014 one, because I can't be away from my family that long. On the other hand, we're still playing a bunch because each booking now typically corresponds to ~4x the amount of playing that it did when we were playing single evenings.
(As before, the code and raw data is on github. If I hadn't uploaded it in 2013 I doubt I would have had the code around, and I definitely wouldn't have put in the time now to redo it.)
I've been seeing people linking to this study to argue that you should have fewer kids:
We recommend four widely applicable high-impact (i.e. low emissions) actions with the potential to contribute to systemic change and substantially reduce annual personal emissions: having one fewer child (an average for developed countries of 58.6 tonnes CO2-equivalent (tCO2e) emission reductions per year), ... we find that ten high school science textbooks from Canada largely fail to mention these actions ...
There are a lot of reasons that this isn't a good way to look at the question of having kids more...
I spent most of July working on a project to evaluate risk from AI that is smarter than humans. I posted updates as I went  but intended to write up a summary with conclusions when I finished. Unfortunately things petered out at the end: I started applying to jobs, wanted to finish a bunch of house projects, and kept waiting for one final set of conversation notes.  The more I put off the final write-up the more I kept putting it off, and now it's September. So, in the interest of just writing the thing up, here's where I am now:
Summary: I'm not convinced that AI risk should be highly prioritized, but I'm also not convinced that it shouldn't. Highly qualified researchers in a position to have a good sense the field have massively different views on core questions like how capable ML systems are now, how capable they will be soon, and how we can influence their development. I do think these questions are possible to get a better handle on, but I think this would require much deeper ML knowledge than I have. more...
When I work I keep two kinds of notes:
Short summary notes aimed at people who are interested in what I'm doing (boss, coworkers, me way in the future trying to figure out what I was working on then)
Verbose running notes where I write everything down about what I'm currently doing. This can include commands I've run  and their output, anything that will help me reconstruct what I was working on, todo lists, or anything else that's helpful to be written down.
The primary difference between these isn't access (both are readable by any of my coworkers) but audience (who I expect to be reading them).
I've been using Google Docs for my running notes, and while it's not ideal it's pretty good. Some configuration options that I find help a lot:
Redefine "heading 1" to be "monospaced 10pt" and then Ctrl+Alt+1 becomes a shortcut for "code font". Ctrl+Alt+0 is still the default shortcut for normal text.
Turn off the default print layout (View > Print Layout) to remove the large gaps between logical pages. If I could remove the concept of "page" from this all together I would, since it will never be printed out.
Switch the document from "Letter (8.5" x 11")" to "Statement (5.5" x 8.5")" in Page Setup, with 0.1" margins. This lets me make the window nice and narrow. I'd be happier if the page would just re-flow as I changed the size of the window, but this is ok.
The main thing that's still missing is Emacs keybindings: Ctrl+A for beginning of line, Ctrl+D for end of line, Ctrl+D for delete, etc. On Mac this just works, and on Linux it works everywhere but Docs, but I don't know how to get it to work in Docs on Chrome on Linux.
 I also log all my shell history.