Category: blog

Sometimes I run across an older book that’s usually out-of-print, but has exceptional wisdom locked up in its pages. I found this one at my local Half Priced Books. First Edition cover, 1991. The very nature of this book—20 essays about writing by the best SFF authors—makes it hard to review as a whole. I think a better strategy is to look at each chapter in detail. See all of my WSF&F chapter reviews.

Note: there is now a GitHub repository for this project. Get the latest code there, including a downloadable Automator app  After sleeping on this I decided there were a few things I could do better. Having to put raw source in the document was annoying. I looked into several ways to do this, but found Ulysses had the answer. If a line of text is “marked” in Ulysses (that’s the :: notation) it gets exported as its own paragraph, but no other HTML tags are applied.

Note: I’ve updated this app, and you can find out more info in the updated article. Plus it’s even easier to install and set up. Or go directly to the GitHub repository for this project. Ulysses does a lot of things right as a writing tool. But it’s not designed to be a HTML or Markdown editor. It’s also not able to post directly to a blog. But its export friendly nature makes it easy to build helper apps.

On May 27, 2015, The Poisoned Pen, a local bookshop here in the Phoenix area is having a book signing with 17 authors attending. There will also be snacks and giveaway prizes. Authors attending: Stephen Blackmoore, Beth Cato, Wes Chu, Myke Cole, Delilah S. Dawson, Kevin Hearne, Jason Hough, Richard Kadrey, Michael Martinez, Brian McClellan, Naomi Novik, Andrea Phillips, Cherie Priest, Brian Staveley, Sam Sykes, Chuck Wendig, & Django Wexler

Sometimes I run across an older book that’s usually out-of-print, but has exceptional wisdom locked up in its pages. I found this one at my local Half Priced Books. First Edition cover, 1991. The very nature of this book—20 essays about writing by the best SFF authors—makes it hard to review as a whole. I think a better strategy is to look at each chapter in detail. See all of my WSF&F chapter reviews.

This is something really cool: A writing workshop hosted by an actual working quantum physics lab. I applied back in March, and the acceptance emails were scheduled to go out around the beginning of April. I had started to wonder if it was still going to happen. The website hasn’t been updated and I hadn’t received word of either acceptance or rejection. This is something that I’d really like to do.

This is my weekly fitness updates. I’ll be posting one every Monday for the foreseeable future. I update a shared iCloud spreadsheet every day. Follow along! Weight & BMI The numbers say this week was a step backwards. I’m disagreeing because of the way I feel. I have more energy and have been sleeping better. Today’s weight: 192.6 lbs. with a BMI of 28.4. Date Weight +/- BMI Fat March 23 191.

It’s time for my weekly word count check-in. At the end of every week, I post a screen shot from my writing results spreadsheet. This shows the current week and the three before. My week starts on Monday. The numbers are current through Sunday night. I also only average over six days. This allows me one day of no writing that doesn’t impact the weekly totals. I was actually surprised at how much I got done this week.

After using GitHub to contribute to a project the other day, I got to thinking about other uses for Git. One was to keep a backup of my ~/bin folder. I write a lot of one-off scripts to make my life easier. Most of the time they’re under 20 lines and previous versions aren’t really needed. But sometimes1 I break things. Other times I’ll go back and wonder what the hell was I thinking.

I have a few projects up on GitHub, but it’s more of a “code storage” place than a “get work done” place. But the other night I ran across a project that I could make a quick contribution to. Besides helping out the project, I also learned a few things about how pull requests work. Including how to clone a pull request and work with the pull request author directly.