Day 18: mood

I guess one can describe this mode as flat. #mbapr

A blue-tongue lizard lying on outdoor ceramic tiles

πŸ‘¨β€πŸ’» On the Coding Bits blog: Changing gRPC Schemas

πŸ“ On the Workpad blog: First Embed, and Optional Arguments

Watched the MKBHD review of the Humane pin (the Streisand effect is real) and I must say, even if it worked perfectly, I’m not sure it’s for me. Something about having to wear it. Kind of conspicuous, no? Not to mention that it’s primarily a voice UI. I don’t even use the voice assistant on my phone.

I mean, credit to them for trying. But… nah, I’ll pass.

πŸ“ On the Workpad blog: Lists, Hashs, and Loops

Day 17: transcendence #mbapr

An ornate, gilded altar in a medieval Spanish church lit with sunlight and artificial light.

Pocket Cast should start tracking the number of times I tap the 30 seconds back button. It’s usually a good indication that I’m really engrossed in a particular show. That button sure got a lot of action this morning with today’s Stratechery and Dithering.

On Micro.blog, Scribbles, And Multi-homing

I’ve been ask why I’m using Scribbles given that I’m here on Micro.blog. Honestly I wish I could say I’ve got a great answer. I like both services very much, and I have no plans of abandoning Micro.blog for Scribbles, or visa-versa. But I am planning to use both for writing stuff online, at least for now, and I suppose the best answer I can give is a combination of various emotions and hang-ups I have about what I want to write about, and where it should go.

I am planning to continue to use Micro.blog pretty much how others would use Mastodon: short-form posts, with the occasional photo, mainly about what I’m doing or seeing during my day. I’ll continue to write the occasional long-form posts, but it won’t be the majority of what I write here.

My intentions for what I post on Scribbles is more likely to be long-form, which brings me to my first reason: I think I prefer Scribbles editor for long-form posts. Micro.blog works well for micro-blogging but I find any attempt to write something longer a little difficult. I can’t really explain it. It just feels like I’m spending more effort trying to get the words out on the screen, like they’re resisting in some way.

It’s easier for me to do this using Scribbles editor. I don’t know why. Might be a combination of how the compose screen is styled and laid out, plus the use of a WYSIWYG editor1. But whatever it is, it all combines into an experience where the words flow a little easier for me. That’s probably the only way I can describe it. There’s nothing really empirical about it all, but maybe that’s the point. It’s involves the emotional side of writing: the “look and feel”.

Second, I like that I can keep separate topics separate. I thought I could be someone who can write about any topic in one place, but when I’m browsing this site myself, I get a bit put out by all the technical topics mixed in with my day-to-day entries. They feel like they don’t belong here. Same with project notes, especially given that they tend to be more long-form anyway.

This I just attribute to one of my many hang-ups. I never have this issue with other sites I visit. It may be an emotional response from seeing what I wrote about; where reading about my day-to-day induces a different feeling (casual, reflective) than posts about code (thinking about work) or projects (being a little more critical, maybe even a little bored).

Being about to create multiple blogs in Scribbles, thanks to signing up for the lifetime plan, gives me the opportunity to create separate blogs for separate topics: one for current projects, one for past projects, and one for coding topics. Each of them, along with Micro.blog, can have their own purpose and writing style: more of a public journal for the project sites, more informational or critical on the coding topics, and more day-to-day Mastodon-like posts on Micro.blog (I also have a check-in blog which is purely a this-is-where-I’ve-been record).

Finally, I think it’s a bit of that “ooh, shiny” aspect of trying something new. I definitely got that using Scribbles. I don’t think there’s much I can do about that (nor, do I want to πŸ˜€).

And that’s probably the best explanation I can give. Arguably it’s easier just writing in one place, and to that I say, “yeah, it absolutely is.” Nothing about any of this is logical at all. I guess I’m trying to optimise to posting something without all the various hang-ups I have about posting it at all, and I think having these separate spaces to do so helps.

Plus, knowing me, it’s all likely to change pretty soon, and I’ll be back to posting everything here again.


  1. Younger me would be shocked to learn that I’d favour a WYSIWYG editor over a text editor with Markdown support ↩︎

Day 16: flΓ’neur

One extra flΓ’neur not in frame. #mbapr

Photo of a tour group of roughly 20 people with a tour guide giving an explanation of some old white marble facade.

Went to Phone Phix and got my phone phixed. πŸ™ƒ

Got the USB-C socket cleaned. Cost a bit but the USB-C plugs are staying in place now, so I call that a win.

Love the new categories feature in Scribbles. Went back and added them to the posts on Coding Bits and Workpad. They look and feel great.

Screenshot of Scribbles post screen showing three posts, each with a different category with a different colour.

Took a while to troubleshoot why my shell script wasn’t running in Keyboard Maestro. Turns out I needed to add #!/bin/zsh -l to launch it with ZSH, with the -l switch to read my zprofile dot file.

Screenshot of a Keyboard Maestro "run shellscript" step with the hash-bang line set to /bin/zsh with the -l switch

Day 15: small #mbapr

A beetle with a copper shell on a tiled floor

πŸ”— The Worlds of Podcasting

On it, their producer was lamenting not having somewhere to post a link to something being spoken about. No mention of show notes because I’m not convinced “big podcast” even knows they exist.

I’ve complained about this before and I haven’t seen any improvements. It’s as if the concept of making show-notes or even a website containing the links you mention on your podcast never cross these producers minds. That it’s perfectly okay to read URLs aloud and expect people to remember. It’s such an odd phenomenon.

πŸ‘¨β€πŸ’» On the Coding Bits blog: Go Unit Test Naming Conventions

Seems like the signs of middle age for a Pixel phone is that the USB-C contacts lose their grippiness. I’ll have to get mine cleaned again. Finding my phone didn’t change overnight is not a great experience.

Day 14: cactus

Okay, I admit that it’s quite a stretch to call this a cactus. I do think it’s some form of succulent, or at least a plant that’s suitable for hot, dry climates, so I’m going to go with it. #mbapr

A succulent in a pot with thick, broad leaves.

Mum found a bunch of tapes of us making radio shows when we were kids. I’m digitising them now using this radio, which is the only tape player available to me. Not pictured is the Nuc running Linux, recording the audio (forgot how painful dealing with Linux audio on the command line is).

A radio and cassette player connected to a USB interface with a few cassettes in the foreground.

Day 13: page #mbapr

Page from a journal with a hand written date of 15 July 2023 in the top left in blue, and in the centre in all-caps, the handwritten phrase 'Page Intentionally Left Blank'

πŸ“ On the Workpad blog: Tool Command Language: Macros And Blocks