Two simple things I like about Scrivener and Ulysses

When it comes to writing fiction (and specifically fiction), there are two things I like that both Scrivener and Ulysses offer that, perhaps surprisingly, very few other writing apps do. One is nice to have, the other I consider more essential.

  1. A list of scenes that can be re-ordered. Both programs show a list of scenes to the left of the main writing window, acting as containers for scenes/chapters. You can move them around in any order that you want. I rarely move scenes around, but having them visually laid out next to the main editing window helps me get a visual overview of a novel, a case where technology really does offer something you can’t easily replicate going old school with pen and paper (or typewriter).
  2. Indents on paragraphs. This might seem trivial, but hear me out! When I write blog posts like this one, I hit Enter (or Return, for Mac purists) and a new paragraph begins. This can work in fiction, too, though you’ll never see a book printed this way (it would add many more pages and drive up costs on paper books, for one). In paper books and their digital brethren, the first line of each paragraph is indented to distinguish it from the one before. If you use a typical markdown editor, hitting Enter will only start a new line, it won’t add a blank line (WordPress does not use Markdown and is coded to add the blank line automatically). You need to hit Enter twice for that. In fiction, you can have a lot of short paragraphs, such as when there is a back-and-forth dialog between characters. This means you are constantly having to hit Enter twice to properly separate paragraphs and avoid getting what looks like a wall of text. Ulysses cheats by using a modified version of Markdown that allows indents on the first line of a paragraph. Scrivener avoids this entirely by adopting a Word-like WYSIWYG approach.

I could, for example, use Obsidian, a free Markdown editor I am using for notes, to write a novel. There’s even a community plugin called Longform made just for this purpose. But there’s no support for indents, so I’d be doing the double Enter thing, and in my experience it breaks flow just enough to be consistently annoying. Maybe I’ll try again as an experiment on a short story or something, because there are aspects of both Scrivener and Ulysses I don’t like, so finding an alternative to both would be nice.

And for the extra-curious, here are some of the things I don’t like about each:

Scrivener:

  • Does not handle cloud saves well at all
  • Cumbersome, ugly and unconventional interface (yes, even on the Mac)

Ulysses:

  • No Windows version
  • Requires subscription (I think it’s a great example of how a subscription is great for developers while being a poor value for the user)

Again, both of these things may seem relatively small, but together they add a lot to make the experience of writing fiction a better one for me. And I really can’t think of other writing apps that offer both, which is kind of weird!

Scaling new heights of ERR

I was up at 5 a.m. this morning due to gallstones. Not my gallstones, mind you.

Since I was up, I went about my usual morning routine, which includes the daily weigh-in on my trusty Fitbit Aria scale. There were shenanigans.

It began after the weigh-in, when it failed to sync my weight to the Fitbit Google hivemind. Yesterday I installed a new Wi-Fi hub and because the app for setting it up would not allow spaces in the Wi-Fi network name, it changed slightly, thus forcing us to manually reconnect every device on our Wi-Fi network. Hooray.

Remembering this, I figured I’d have to run the setup for the Aria scale to get it connected to the new space-free Wi-Fi network.

  • I put the scale in setup mode
  • I launch the Fitbit app on my phone
  • The Fitbit app says the Aria scale is no longer supported, set it up through a web browser, chump
  • I follow the link provided
  • I go through the process, which requires treating the Aria as a new device
  • I get to the last step, entering the password for our Wi-Fi
  • I watch as it joins the network
  • I watch as it fails with an ERR message. That’s all, just ERR. Like it is clearing its throat.
  • I start the process over from the beginning, as there is no other way to do just the joining part again
  • I get another ERR
  • I try again, more ERR
  • I get angry
  • I become resigned
  • I decide not to spend more of my time chasing an unspecified error on no-longer-supported hardware
  • I record my weight, because it still actually does that part
  • I think about getting a non-Fitbit scale again

UPDATE: I remembered the Aria connects via Wi-Fi via a USB receiver on the Windows PC. Said PC was not connected to the new Wi-Fi network, so maybe that was the issue? I have fixed this and will try getting the scale working again tomorrow. It’ll be fun.

The Great Culling of 2022 Continues

Yesterday I trimmed down a few more subscriptions. Yes, I am the poster boy for subscription fatigue. Beware, SaaS purveyors!

  • After dropping the Todoist sub, I have now also dropped the TickTick sub. I’ll see how the free version goes, but if it proves too limiting, I’m already running Microsoft’s To Do, and it seems to meet my needs, even if it’s “My Day” feature is a bit weird compared to a more conventional “Today” list (mainly, you have to move stuff to My Day, as it always starts blank).
  • Apple emailed me announcing my already expensive Apple One Premier subscription was going from $33.95 a month to $37.95 a month. Since they made $20 billion in PROFIT just last quarter, I opted to slim down to the Apple One Family package for $24.95 per month. I suspect the company will manage to scrape by. And I’ll save $13 by not getting stuff I don’t need, like:
    • Fitness+: I have literally never used this.
    • Apple News+: An ad-riddled hellscape, even as a paid service.
    • 2TB iCloud storage: I’m using 150 GB and only because of my photos. The new plan gives me 200GB. Since I’m now using OneDrive for photos, this shouldn’t be an issue.

Apple has become a fat, greedy company that seems determined to worsen the customer experience in exchange for squeezing as much revenue out of everyone as they can. I don’t think the company is going to fail or anything, but I think the long, gradual decline has begun. Maybe the ghost of Steve Jobs will visit Tim Cook at Christmas and be all, “WTF you doing, Tim?” and then Tim will retire on the few dollars he has put aside. BUT NOT $48 PER YEAR OF MY FEW DOLLARS. TAKE THAT, TIM.

Anyway, the number of subs I have is much slimmer now than at the start of 2022. My email is no longer full of newsletters I no longer read. I feel much less burdened now. And I like it!

The most 80s thing I’ve seen since the 80s

I never knew there was a video for the song “Funky Town” but of course there is. And it is magnificently 80s, from the pink jumpsuits to the “sophisticated” video effects, the line that sounds like the intro to a 1980s video game and, of course, the robot (dance). It truly has it all.

It’s also a pretty weird song, when you think about it.

Even the YouTube thumbnail is amazing!

https://youtu.be/jPF59O7_qw0

Flickr: Now with more sh*t

I got an email from Flickr inviting me to use their print services to print out and cherish/send my photos to others.

This is how they are attempting to persuade people to do this:

Did I have a “How do you do, my fellow kids?” moment and miss how “sh*t” is now the cool, hip way to say “shot”? But also it looks like “shit” so it’s…funny? Edgy? Dumb?

Dumb.

UPDATE: I have taken the newsletter to its logical (rear) end. Behold:

Run 730: The first (unofficial) winter run of 2022

Today was chilly! It was actually freezing when I headed out, but was a balmy 2C when I started (and ended) my run. I opted to wear three layers up top (jacket, long sleeve and sleeveless shirts) and shorts. This proved fine and I didn’t feel I was overdressed once I warmed up. The extra layer was especially nice for the walk to and from the lake.

The trail was a mix of dry, wet and frosty, but because there’s been no rain for a few days, there was no ice buildup. I did approach stairs with caution. The new grid mesh on top of the dam prevented any ice capades there. Sadly, the fountain has been locked up until spring. No post-run sips until March or something.

I chose to run at a deliberate pace to keep the BPM down, and it sort of worked. My overall BPM was higher than Monday at 155, but only slightly. My overall pace was slower, naturally, at 6:05/km, but I’m fine with that. I experienced no issues during the run, though I think the general cold was starting to tucker me out by the final km. There was no big final push here, just a steady roll to the end.

Overall, I’m happy with the result.

I’m less pleased that the watch once again failed to track my BPM for an entire km, though. /me scowls at Apple Watch.

Stats:

Run 730
Average pace: 6:05/km
Location: Burnaby Lake (CCW)
Start: 10:24 a.m.
Distance: 10.03 km
Time: 61:05
Weather: Sunny
Temp: 2ºC
Humidity: 69%
Wind: light
BPM: 155
Weight: 159.4
Total distance to date: 5385 km
Devices: Apple Watch Series 5, iPhone 12, AirPods (3rd generation)
Shoes: Saucony Peregrine 12 (62 km)

My unwritten, unrecorded and undoubtedly underappreciated concept album: 13 Unlucky Songs

Today, while on my run, several songs from The Magnetic Fields’ 69 Love Songs came up on shuffle play. I suddenly thought of ripping off the concept with a scaled down, differently-themed album using the same general premise. I give you…

13 Unlucky Songs

  1. Under the Ladder
  2. The Crack on the Sidewalk
  3. Dropping the Mirror
  4. Break a leg
  5. My Black Cat
  6. Shoes on the Table
  7. Don’t Test the Umbrella
  8. Rocking Chair
  9. The Stopped Clock
  10. 1954 Calendar
  11. The Owl is Just What It Seems
  12. Green Room
  13. The Hat on the Bed

Also, I accidentally learned about some superstitions I was unaware of while coming up with song titles. Unintended education.

Now to record this in Garage Band, right after I learn how to make music, since my knowledge of this is currently close to zero. I mean, I know what notes and sheet music are. I know guitars are cool. That’s probably enough, right?

Run 729: Trail of destruction

We had a big storm on Friday, with torrential rains, high winds and all the fun things you associate with big storms. While one now ex-tree on the Avalon Trail had already been cut up, the trail was still littered with twigs, smaller branches and other bits of debris. I wonder how terrifying it would be to run in the middle of a storm like that?

Today, I opted to run clockwise (the “easy” route) for my first Pacific Standard Time (boo) run of the season. It was my coldest run of the year at 4C and I opted to wear my windbreaker running jacket and a long-sleeved short underneath. I still wore shorts. And it was fine. I probably could have opted to wear a shirt underneath, which would have made it easier to check the watch.

I actually had no issues during the run, other than having to take an unplanned loo break at around the 3 km mark. I kept my hands tucked into the sleeves of my jacket until around the 4K mark, then they were sufficiently warmed up for the rest of the run. My pace was better than expected, though overall BPM was higher, too, at 153. Not surprising, given the much cooler conditions.

Still, better than doing the same in the rain!

Special bonus: At 4C, I barely generate any sweat. I didn’t even realize this until I got home.

A shot showing the relative calm at the lake (no wind is nice, too):

Stats:

Run 729
Average pace: 5:52/km
Location: Burnaby Lake (CW)
Start: 11:31 a.m.
Distance: 10.04 km
Time: 58:57
Weather: Cloudy
Temp: 4ºC
Humidity: 63%
Wind: light
BPM: 153
Weight: 159.9
Total distance to date: 5375 km
Devices: Apple Watch Series 5, iPhone 12, AirPods (3rd generation)
Shoes: Saucony Peregrine 12 (52 km)

The best and worst running conditions, 2022 edition

Previously:

The best worst running conditions: 2016 edition (April 27, 2016)

Bad weather running: the list (updated) (July 10, 2012)

Bad running weather: the list (July 13, 2011)

Due to climate change and certain incidents, I feel it’s time to update the list again. Here are the best/worst running conditions. Unlike the previous entries, I’ve numbered them from best to worst, to keep things more positive or something. For the record, only the top three are really what I’d call “good” running conditions.

  1. Overcast and light breeze. This is actually ideal conditions. It is usually never too cold or warm when the weather is like this. Temperature-wise, we’re looking at around 15C.
  2. Moderate wind. Moderate wind is fine. I have a cap that stays in place now.
  3. Warm sun. Warm is no big thing. I’m talking about 20ºC or thereabouts.
  4. Light rain. You might think light rain would be nice, but it really isn’t. You still get soaked, and in the summer there’s no real way to dress for it. And it still feels cold(ish), even in mid-July.
  5. Snow. I’ve only run in light snow a few times, and it was fun. Light snow is shallow and fluffy, so it’s easy to move through. I’m thinking a foot of snow would probably be less so.
  6. Cold rain. Cold rain means cold hands and if you wear gloves they need to be waterproof. Cold rain is never fun. Plus my nipples are weirdly sensitive to the cold now and cold rain is like torturing them. Poor little nipples. UPDATE FOR 2022: It turns out the nipples are more sensitive to moisture more than the cold, as The Nipple Issue™ returned in Summer 2022.
  7. Hard rain. This has the potential to wreak havoc with any non-waterproof items you may be carrying, and it’s hard to see if you wear glasses. I wear glasses.
  8. Extreme cold. I’ve run in sub-freezing conditions and been fine. I’m thinking Arctic tundra-type cold here.
  9. Heavy wind. The resistance means you work a lot harder to achieve the same result, and my cap has to be on tight enough to cut off circulation, so it doesn’t fly away. This is pretty rare where I run, though. And I don’t run during actual windstorms due to the very real danger of flying (tree) debris.
  10. Hot sun. When it’s hot, my body feels like a furnace, and I’m left parched as all get-out. Dry mouth and lips are yucky. By hot, I mean high 20s and up. While it still gets hot in the summer, a new contender has arrived to usurp it. Keep reading!
  11. Hard rain and heavy wind. Likeliest weather to make me wonder to myself, ‘What was I thinking?’ when running.
  12. Hot sun and heavy wind. Or “What would it be like to do a run on a windy day in the Sahara?” Heat dries you out, the wind makes it harder to run and dries you out even more. Bleah. This combination is, however, pretty rare.
  13. Hail. Getting pelted by little ice rocks is unpleasant. I’ve been caught in hail twice and did not like it either time. Still, twice since 2009 is not bad.
  14. Cyclists. I have grown to loathe anyone on a bicycle, especially since the area where I run most frequently–Burnaby Lake–forbids bicycles, but cyclists show up anyway, sometimes in packs. They tend to be either little kids who will wobble suddenly and unpredictably in front of you, or jerks who power through as fast as they can pedal, oblivious to the presence or safety of others.
  15. Dogs. See here. I’ve had a dog knock me down while running. The weather has never done this.
  16. Tree roots. See here. I’ve only tripped and fallen over a tree root while jogging at full speed once, but once was enough. Fortunately, the resurfacing of the trails at Burnaby Lake means almost all exposed roots are now gone.
  17. Hot sun/heat and high humidity. This is the new entry for 2022 (the tree root happened in 2016, but the previous version of the list was written pre-root). See how Hot sun is way up there at #10? The heat/high humidity combo is so much lower because IT IS TERRIBLE. While I don’t suffer from a parched mouth in this weather, the combo of 30C+ weather and extremely high humidity in the summer of 2022 made running a horrible slog, no matter what the time of day. It was only just less horrible, depending. And it happened for nearly the entire summer, earning its hallowed spot here.