I love short books on writing, it’s so easy to blast through them and then apply their lessons–provided they include advice on overcoming procrastination, of course.
Weiland’s slim how-to covers everything from cultivating the mindset for ideas, establishing good habits and how to deal with the inevitable feelings of “my writing sucks now and forever more.”
The specific tips for avoiding writer’s block itself are copious and for the most part familiar to anyone who may have read similar guides, ranging from the easy to follow (“Take a break”) to the may-need-a-few-tries-to-work (“Show up every day” and “Just start typing”).
This is another perfectly fine book for a new author to peruse, or for anyone who yearns to write but is unhappy with both the quality and quantity of their output. There’s nothing revelatory, but Weiland’s writing style is light, engaging and the brevity of the work (and use of lists) makes it serve as a handy reference you can return to time and again
Recommended.
Now I just need to write something other than reviews on writing books. 😛
On a whim I plugged in my old Filco 87-key keyboard with brown switches to see how they felt after not using the keyboard for awhile and it’s actually better than I remember. The keys are tactile without the same CLACK as blues, but still satisfying to a certain degree, and less noisy.
With the Filco still plugged in and in the mood for some typing, I did a search for “learn to type” and landed at typingclub.com. It was eager to invite me to take the first lesson, which consisted of typing F and J a lot (the home keys, as the billions of people who can touch type already know). I dutifully went through Lesson 1 and got the following results:
I’m not sure what real accuracy is, other than the apparent opposite of fake accuracy. But look, I passed all the requirements and was invited to move on. This scares me, because Mavis Beacon started out very encouraging, too, before basically saying I was slow and a bit dumb, but I’ll let you skip ahead so you don’t cry and make a scene, okay?
26 wpm compares to my usual three-fingers-look-at-the-keyboard-a-lot method’s average of 45 wpm or so. The gap between the two is sadly not that great to close, testimony to how slow I currently type.
I may try Lesson 2 or another program, or just recall Mavis’s cruel smile and switch to voice dictation. We’ll see.
Run 594 Average pace: 5:43/km Location: Burnaby Lake (CCW)
Start: 12:08 pm
Distance: 5:03 km
Time: 28:51
Weather: Cloud, some sun
Temp: 19-20ºC
Humidity: 54%
Wind: light to moderate
BPM: 163
Weight: 161.7 pounds
Total distance to date: 4550 km
Devices: Apple Watch, iPhone 8
Today’s run was mostly a repeat of Saturday’s, but with a few minor differences–it was very slightly cooler, the clouds managed to obscure the sun for the entire run (it cleared up after on the walk out) and I improved my pace by another three seconds. My BPM was also up slightly to 163, but that’s to be expected as I worked a little harder.
A pleasant breeze was blowing for most of the run, providing a nice bit of refreshment along the way.
It was also kind of crowded, as it usually is on stat holidays, with many people out for a walk, as well as a larger than normal number of joggers. This wasn’t really an issue, as even the “oh, I didn’t see you!” people were able to get out of the way before an inevitable collision. Strangely, at least three male joggers were topless. I say this was strange because it’s rare to see any guy running topless, let alone a gaggle of them. The first one zipped by me before I began my run, as I was looking for a place to pee (I’ll get to that in a moment).
He had a perfectly bronzed and perfectly chiseled body, so obviously did more than run. He didn’t have any earbuds or phone with him. He was here to run, not enjoy himself. He looked very serious. And he wasn’t jogging, he was running. He zoomed by. I estimated that I would see him again somewhere on the Cottonwood Trail, once I got started.
I was delayed a few minutes because I had to pee (no surprise) and the Jiffy John® was occupied (also no surprise). But when the occupant vacated the loo, a bee buzzed me and I backed off to prevent getting stung and the like. Then I noticed more bees gathered around the Jiffy John, including some buzzing along the bottom of the door, which has a generous-sized gap (generous for a bee, anyway). I contemplated the possibility of sharing the potty with one or more bees and maybe getting stung before the run.
I decided to pee elsewhere.
There’s a big tree on the other side of the dam and in the summer the surrounding foliage provides ample cover, so I relieved myself there and headed off.
After that it was pretty much smooth sailing, with no discomfort, no issues. I started slower so there weren’t the dramatic swings in the splits like Saturday, bit overall my pace improved. This was even nicer as counter-clockwise is the “hard” way.
I also ran more aggressively post-run, putting in what I estimate as probably about three km of running after officially finishing the 5K. I’m probably ready to try a 10K. My knees are afraid.
This is a perfectly cromulent book on outlining a novel and Fox goes into detail on two popular methods, the traditional three-act approach and the perhaps less-familiar story circle.
Running with the gardening metaphor, Fox provides step-by-step instructions and illustrates them with examples from several popular movies (relying primarily on Star Wars) and also drawing from his own work–including examples where he failed, and then learned from the failure.
Each chapter has exercises to follow at the end and Fox knows a lot of people will just read straight through, so he has thoughtfully included all exercises again at the end of the book.
Overall, there’s not much more you could ask for in a book about outlining a novel. Fox explains everything in a clear manner, provides examples, and even throws in a bit of neuroscience here and there. Despite all this, I never found the book overly engaging, perhaps because I’ve always resisted outlining my stories–and I can’t claim they’ve been better for this lack, either.
Still, don’t let my own indifference sway you–this is a well-constructed template on how to outline a novel and would serve any new novel writer well.
The Canada Line is the ALRT that runs from downtown Vancouver to Richmond, splitting off to either the airport or central/”downtown” Richmond. It opened for service in 2009 and one of its intended functions was to help move people from the airport to Olympic venues during the 2010 Winter Olympics.
Obviously the construction of a subway is always going to be disruptive to the neighborhoods it goes through, but the Canada Line’s first bad design was the decision to use cut and cover tunnels for most of its route. Cambie Street is the main route the line follows and it literally follows it–being cut and cover, they dug up Cambie Street, keeping two of its six lanes open during construction–and laid down the subway route along the road, following the same route, including a prominent “bulge” around Queen Elizabeth park. Businesses sued over the construction, some went under or moved and in the end it was declared such a mess that the entire Millennium Line extension from VCC-Clark to Arbutus is going to be a bore tunnel.
But the construction was only the first tangible aspect of the bad design. Once open, the line revealed its other flaws to the public. Namely, it was built on the cheap and with no thought put into expansion.
The system only runs two-car trains, severely constraining capacity (it’s already maxed out at rush hour)
Stations are very small and often have multiple bottlenecks, leading to serious crowding issues
Fare gates are often too close to the platform, again because of the tiny size of the stations
The small stations means that even if they expanded trains to four cars–which they could do anytime–there would be no room for the trains at any of the current stations. They would literally have to dig out new space everywhere except for the above-ground stations in Richmond. Compare this to the Expo Line opened in 1986, where all platforms can accommodate six-car trains, even though they only ran four-car trains for many years.
Adding insult to injury, the Canada Line even started removing seats from some cars to allow more people to squeeze in, a terrible solution to overcrowding that will only drive (ho ho) people to seek alternatives. They fortunately stopped this after gutting a couple of cars, but the fact that they did it at all shows how inept the leadership is.
The terminus Brighouse station in Richmond is specifically not designed to accommodate any expansion of the system. When the train leaves the previous station, Lansdowne, it switches over to a single track. The Brighouse station is built specifically around that single track, meaning any expansion would require a massive and expensive retrofit. Compare this to the Millennium Line, which anticipated a future expansion to the Tri-Cities called the Evergreen Line, leading them to build the base infrastructure for a third platform at the Lougheed station, where they expected the Evergreen Line to hook up to the rest of the system. When funding finally got approved for Evergreen–more than a decade later–crews were able to build on and around the existing third platform, saving time and money.
The trains are seriously noisy when going around corners, the wheels shrieking like crazy. This does not happen to the same degree on the underground sections of other lines.
Even the choice to go with a Korean manufacturer was short-sighted, as it meant the system could not integrate with the two existing SkyTrain lines, perhaps saving money in the short term, but hobbling any overall integration in the long term.
Much of this can be laid at the feet of the former BC Liberal government, who wanted the line built cheap and fast. They got both of those, but what they didn’t get was the unspoken third part–good.
Fixing the Canada Line would be difficult and costly, but it will likely have to be done eventually, simply because it’s already reached its capacity. There’s no happy ending here.
Run 593 Average pace: 5:46/km Location: Burnaby Lake (CW)
Start: 12:51 pm
Distance: 5:02 km
Time: 29:01
Weather: Sun and cloud
Temp: 18-22ºC
Humidity: 60%
Wind: light to moderate
BPM: 161
Weight: 162.9 pounds
Total distance to date: 4545 km
Devices: Apple Watch, iPhone 8
After battling and re-battling a cold, I was finally back out running for the first time in two weeks.
Surprisingly, my pace was also three seconds better. I find this doubly surprising, not just because I wasn’t expecting to be faster after a two week layoff, but I was deliberately not trying to push in the early part of the run, to minimize issues arising from rust/decrepit age and so on.
The knees made their presence known early on, but after a few km they were no longer an issue. I also experienced no cramps or other problems and my stamina held up nicely. Overall, a solid run and under welcome conditions–mild temperatures, a decent and refreshing breeze, and no tangible smoke haze (it’s still there, but it’s not enough to really notice–the mugginess and most especially the discernible smoke odor are currently absent).
I went clockwise, so delighted in spending much of the run on the freshly-resurfaced areas. The small dogleg just before you emerge alongside the sport fields is still closed off, though. I have no idea why this particular trail repair is taking so long, but I suspect it will look mostly the same when completed, but still be different, somehow (my hunch is shoring it up so it doesn’t flood, so it may be raised up a bit).
The one odd part of the run, such as it is, was during the third and fourth km. My pace dropped off significantly–more than I would have guessed if you had asked–and I can’t pin it to any one thing. Here are the splits:
5:39
5:42
6:01
6:00
5:30
The first two km are consistent and then my pace drops a whopping 19 seconds, holds there, and then improves by an even more impressive 30 seconds as I move through the home stretch. I’m not surprised the pace picked up in the final km, as I was pushing at that point, but by 30 seconds seems a bit nutty.
Other than sudden slow leg syndrome (SSLS), this was a perfectly decent run, especially after the two weeks off.
As a bonus, the bridge at Silver Creek is finished and the replacement has a rustic charm the older one didn’t really have.
A recent email from Zinio–a digital magazine store–arrived and the enticement in the subject line rather suggests the person dispatching their mass emails might want to subscribe to Grammar Weekly*.
* It’s entirely possible there really is a Grammar Weekly magazine. I didn’t check, though.
Fizzled after a few weeks. I realized I hadn’t logged in for the better part of a few weeks and canceled my subscription.
Unlike days of yore, the cancellation process no longer makes you go through a series of steps that gently plead with you to change your mind. Instead, you click Cancel Subscription, get a Yes/No pop-up to confirm and that’s it.
I certainly can’t say I didn’t get plenty of enjoyment out of WoW, but one of the main attractions of MMOs for me is the early (yes, early!) character growth and exploring the world and these things have grown very stale in WoW, through a combination of the game not changing much for my playstyle and me just playing the heck out of it for nearly 14 years.
I’d like to find another game with a big world to explore, but I’m not really sure there’s one out there that would fit what I’m looking for, because I’m not even sure what I’m looking for. I’d like a game with other players around–like an MMO–but not too many to make it feel crowded. I don’t want to have to line up to kill ten bears. I don’t actually want to kill ten bears particularly, either.
I know there are online survival games and a nigh-endless sea of clones building (ho ho) on what Minecraft started, but I’m nearly as out of touch with gaming as I am with pop music.
I am old.
Maybe I’ll just start drawing more. It’s simple, kind of soothing and doesn’t require a subscription.