Thanks to all who helped with my job search. I started work with a new client today, commuting on the Tube for the first time in eight years.
Speaking of the Tube, I hate that all news coverage of Coronavirus features a photo of someone wearing a face mask on public transport even when the news isn’t about the UK.
Every time I mention C to someone, I think of Euan’s mastery of undersharing. I remember first hearing he had a cat after working with him for four years.
Speaking of dad chat, I can’t wait to invest in a Father-Son Podcasting Microphone:
Well, it’s tough, you know? I mean, there’s no book you can read about being a dad.
Actually, there are several.
I’ve always had a soft spot for macOS indie developers. I have been a customer of LaunchBar, NetNewsWire (and its recent update), DropDMG, Airfoil, SuperDuper!, Interarchy, OmniGraffle, DiskWarrior, BBEdit, Transmit, SpamSieve and TextMate. This is partly why I enjoyed hearing about John Siracusa’s new apps and why I’m now trying Craig Hockenberry’s new notepad app—Tot—after reading John Gruber’s summary of it.
I secretly wish I had an idea for an app of my own.
I read Ryan Singer’s “Shape Up: Stop Running in Circles and Ship Work that Matters” and—despite unnecessarily dismissing existing agile practices in the foreword—found a lot I agreed with.
I’m increasingly convinced of the need for something like shaping before something is picked up by a development team. The struggle, as Singer writes, is getting the right level of detail: neither too abstract nor too concrete.
I was especially intrigued by the idea of appetite, not estimation as I’ve often found people unwilling to reveal truly how much they want a particular feature or project and drawing this out up front is extremely appealing.
The idea of pitch documents that can be reviewed asynchronously by members of the team sounds very similar to a Request For Comments (RFC) process (e.g. RFCs for changes to Rust, Yarn and Ember; see also Gergely Orosz’ “Scaling Engineering Teams via Writing Things Down and Sharing - aka RFCs”): something I am a huge fan of if you’re looking to introduce both rigour and equitability when proposing significant changes to teams and systems.
We took a trip to IKEA to get C a new cot and a Billy bookcase (one of which is sold every 5 seconds). I spent a lot of time in the kids’ section, fawning over the train sets, toy kitchen and its many, many accessories. Luckily for my wallet, C is still too young for them.
As one of my many “jobs to complete before returning to work”, I lovingly re-seasoned our wooden chopping board following J. Kenji López-Alt’s advice. There is something therapeutic about rubbing a wooden board with coarse salt and half a lemon.
The major thing E and I have been working on is getting C out of our bedroom and into his own room in the hope we can all improve our quality of sleep. Not wanting to confuse him with too much change at once, we first moved ourselves out and onto our sofa bed. When contemplating the next step, I was reminded of the 2,000 year old problem of the wolf, goat and cabbage.
In turn, this reminded me of a great London Computation Club meeting back in 2015: “The New Turing Omnibus, Chapter 58: Predicate Calculus” when Tom showed us how to use first-order logic to mechanically resolve the problem.
Bonus trivia: that was the same meeting that Chris announced his work on his programming language, Sentient.
E and I have many phrases that would be incomprehensible to others but a recent favourite is the following emoji-only message:
Of course, this translates to “the clown is down” which is a quote from The Simpsons’ “The Parent Rap” we’ve distorted to mean “our baby is asleep”.