On the other hand, once other people are involved this isn't entirely up to me. One place this comes up a lot is parenting: I don't want to write things about my kids that they don't (or won't) want public. This is especially tricky if I write a post about something we've tried which worked well in part because the kids did a good job with it, and then later they stop doing a good job.
My kids like it a lot, and Anna and I decided to build something for it. Anna wanted to make a house, and I sold her on making a triple decker. These are three-unit buildings, one on each of three floors, that are common in Somerville and other older Boston-area neighborhoods.
I do have a lot of stuff by my feet:
The very lowest notes tend to be boomy, while the higher notes are just not very useful in playing the kind of music I play. I use a bit over five octaves (B0-D6, 31-1175 Hz).
At the same time I've been wanting to have a separate keyboard for taking to gigs. The ideal, really, would be to have an entire duplicate rig, which would halve the amount of setup and teardown involved, since I would only need to set up and pack away at gigs. This is enough extra effort and expense, however, that for now I'm just duplicating the keyboard (and stand).
I decided to get a Yamaha P-121:
It is the discontinued 73-key version of the P-125, which is the ~current version of my P-85. [1] Which made it a bit hard to find one, but there was one new-in-box shipping from Japan on eBay. I was a bit nervous, but it worked out fine.
With the Bolt, everything was fine except charging.
With the Model 3, the only good part was the charging.
The car acted like a car, which is what I want. No overly minimalist design where I can't find anything, no automatic wipers that fail to detect spray from the road, and especially no too-smart cruise control with phantom braking. Just a car.
For each analysis I make a local directory,
~/work/YYYY-MM-DD--topic/
. These contain large files I'm
copying locally to work with, temporary files, and outputs. When
these get too big I delete them; they're not backed up, and I can
rebuild them from things that are backed up.
Code goes in a git repo, in files named like
YYYY-MM-DD--topic.py
. Most of my work lately has been
going into an internal repo, but if there's nothing sensitive I'll use
a public
one. I don't bother with meaningful commit messages; the goal is
just to get the deltas backed up. If I later want to run an analysis
similar to an old one I duplicate the code and make a new work
directory.
Code is run from the command line in the work directory, which
means that in my permanent
shell history every command I ran related to topic
will be tagged with ~/work/YYYY-MM-DD--topic/
.
Work | Nucleic Acid Observatory | |
Work | Speaking | |
Band | Kingfisher | |
Band | Free Raisins | |
Band | Dandelion | |
Code | Whistle Synth | |
Code | Apartment Price Map | |
Board | BIDA Contra | |
Board | Giving What We Can | |
Spouse | Julia | |
Child | Lily | |
Child | Anna | |
Child | Nora |