All posts by Jamie Todd Rubin

About Jamie Todd Rubin

Jamie Todd Rubin is a science fiction writer, blogger, and Evernote Ambassador for paperless lifestyle. His stories have appeared in Analog, Daily Science Fiction, Intergalactic Medicine Show, Apex Magazine, and 40K Books. He vacations frequently in the Golden Age of Science Fiction. Jamie lives in Falls Church, Virginia with his wife and two children.

Heading to Los Angeles Later this Month

Well, Santa Monica, actually. And it is a whirlwind trip. I’m flying out for work on Sunday, August 10, and then taking the 6 am flight back home on Wednesday morning, August 13. It’s my first work-related trip to L.A. since 2011. I used to go much more frequently, but I burned out on that kind of travel. A 5 hour flight across the country seems twice as long.

But, I always try to look for the silver lining. I’m attempting to finish up the first volume of Manchester’s biography of Winston Churchill before the flight, so that I can spend my 10 hours in the air making my way into the second volume of the biography.

As for my schedule in L.A., the roughly 48-hours that I’ll be in town are already booked solid, mostly with work-related stuff. On Sunday evening, at least, I’m having dinner with friends from high school that I don’t get to see very often.

I have a ton of day-job work leading up to the trip, and so my days of high productivity pulses courtesy of RescueTime will probably continue for a while. I’m guessing they will continue through mid-September. We’ll see.

Introducing open.jamierubin.net

With all of the data I collect about myself, I’ve been wanting to put together a kind of open dashboard that provides a window into the data through interesting visualizations. While my short term plans are nothing like the amazing things happening over at Aprilzero, I have put a very early prototype together of what I am calling open.jamierubin.net.

open.jamierubin.net

Right now, all the site does is make a live query to my Google Doc Writing Tracker spreadsheet, and renders the data in a chart on the site. Clicking on the links above the chart, you can see either the last 30 days of my writing data plotted out, or go back to the beginning of time (over 500 days).

For each visualization I publish, I plan to include a link to the “HOWTO” which will include the code I used and how I pulled the data I needed to make the visualization. That way, if others want to give it a try, there will be at least some documentation.

Eventually, I will come up with a framework for the site, and begin pulling in other data as well. For now, this is a quick-and-dirty prototype of what is possible with just a little bit of code. Take a peek at it and let me know what you think.

Open Beta of My Google Docs Writing Tracker Version 2

I have done a major refactoring of my Google Doc Writing Tracker. Several new features have been added, but the biggest change is that the scripts are not data-driven, making them much easier to setup and configure. If you are using the scripts today, or have been wanting to try them out, you are welcome to install the new beta version.

You can get the files from the beta-version-2 branch on GitHub.

Be sure to read the README as that has been updated to reflect the changes in the system.

New features

  • NEW: A new spreadsheet is available with all of the configuration information built into it. You just fill in the blanks on the Config tab, and the script takes care of the rest. This makes it easier to configure and customize without the need to go into the code.
  • NEW: Option to break down daily word counts into fiction/nonfiction.
  • NEW: Ability to run the scripts in test mode. Allows you to see the results of your configuration in the log without the changes being applied to your spreadsheet.
  • NEW: Ability to customize the order of the columns on the Writing tab.
  • NEW: Ability to customize the names of the tabs in the spreadsheet.
  • NEW: Ability to customize the location and names of the Sandbox and Snapshot (formerly “Earlier”) folders.
  • NEW: Ability to capture time spent writing by integrating with the RescueTime API (experimental).
  • NEW: Ability to generate Daily Almanac summary email that lists stats for the day, and identifies trends and records.
  • NEW: Improved logging in test mode.
  • NEW: Validation of configuration settings.

What I hope to accomplish with the beta

So far, these changes are working very well for me. But I can only really test in my own environment, and because I initially wrote the scripts for me, they may be inadvertently tailored to my environment. In this version, I’ve tried to generalize a lot of the code and make it more flexible and easier to use in other environments.

What I am looking for in this beta is to have people test the scripts in many environments in order to identify any problems, and iron them out before merging this code back into the master branch.

To that end, if you use the scripts I ask that you do 2 things:

  1. Log an issue if you find a problem. Understand that I don’t have a lot of time to work on these scripts. I set aside a chunk of time once a year or so to do a major refactoring like this, but that’s about all I can do. So while I will try to address all of the issues, it may take a while.
  2. If you see a way in which the documentation can be clarified, by all means let me know.

If I do have time, I will try to address the issues as quickly as I can, but that time isn’t guaranteed, and as I say in the README, while I’m making these scripts available to anyone who wants to use them, I don’t have time to support them. You use them at your own risk, so be sure to read the README.

The initial setup can be a little cumbersome and I’ve tried to clarify it in the documentation. Once it is setup, if all goes well, it should just run silently in the background and add to your spreadsheet each day.

If you use the scripts, let me know how they work for you. They work great for me, but of course, they were designed for me and my environment. With this revision, I’m hoping that they work equally well for anyone who chooses to use them.

Going Paperless: How I Simplified My Tag Organization in Evernote (Part 2)

Last time, I talked about how and why I simplified my notebook organization in Evernote. Today, I’ll discuss how I’ve simplified my tag organization. Both are still works in progress, but the tags more so than the notebooks.

To start, let me say that I’ve never been much of a tagger. There are several reasons for this:

  1. Evernote has a powerful search engine that usually allows me to find whatever I’m looking for in just a few seconds.
  2. With such a good search engine, adding tags is usually counterproductive for me, since it takes time to add them to a note, but I can find the note just as easily without them.
  3. Tags have a tendency to grow like weeds. I’d end up with a huge number, and when I look at them, I find that more than half my tags have less than 10 notes associated with them.
  4. With lots of tags, there is a tendency to forget how I’ve tagged something. In some places, it gets tagged “project” in others “projects.” This actually make searching by tags worse. If I search for everything tagged “projects” I don’t get the notes tagged “project” for instance.

That said, I do find value in tagging notes under certain circumstances. Regular readers will recall this diagram:

Evernote Search

I find tags very hand for describing the “who” part of a note. I assign family member names as tags to notes to denote who that note is related to. Tags can sometimes be helpful with the “what” as well, but in all cases, a solid taxonomy is important for preventing uncontrolled tag growth. I’ll talk about that in a moment. First, let me show you what my tags used to look like.

Continue reading

The Start of World War I

I‘m more than halfway through my reading of The Last Lion: Winston Spencer Churchill, Volume 1. Yesterday, as I was about to head out to lunch, I said this on Twitter:

I was referring to the fact that the book was creeping up on the start of the First World War. However, in a remarkable coincidence, it turns out that yesterday, July 28, was exactly 100 years since the official start of World War I back on July 28, 1914. To the day. That is pretty creepy.

Various Updates for Sunday, July 27, 2014

First, sorry I haven’t been as active here as usual over the last week or so. As you might have guessed, things have been busy. But even for me, they have been unusually busy. Two big projects at the day job reached simultaneous critical milestones last week, and that took up a lot of my time. I’ve also been busy writing articles, and working on stories. And on top of that, I’ve been writing a bunch of code. Here is what RescueTime had to say about my productivity last week:

My productivity for the week of July 20

Keep in mind that my productivity pulse is typically in the 65-75 range. When it is in that range, I feel comfortable, and not overwhelmed. Below 65 and I start to feel a little lazy. Above 75 and things start to get a little intense. My average for the entire week was 78. There were days when I was close to 90.

In any case, here are a few updates of possible interest to folks:

1. R.I.P. Maggie: On Friday, we said goodbye to one of our two cats, Maggie. Maggie was nearly 18 years old, and had been healthy her entire life, except for the last few weeks. She had a tumor combined with some other infections. We thought that with some medication  she might rebound, but it wasn’t to be. She was a sweet cat, and will be missed by all of us.

2. Part 2 of my Going Paperless series on how I’ve simplified my Evernote organization will appear on Tuesday. Part 1 covered how I’ve simplified my notebook organization in Evernote. Part 2 will cover how I’ve simplified my tag organization. I had to delay it last week because–well, see the chart above. But it will be out on Tuesday.

3. My latest column for the Daily Beast went live on Thursday. The third piece in my column on quantified self for The Daily Beast went live on Thursday. This piece, titled, “Self-Tracking for N00Bz1 provides a simple 3-part framework to consider for folks who want to investigate self-tracking.

4. I’ve added some features to my Google Writing Tracker. I posted about it on Friday. I’m in the process of doing some major refactoring, and I’m alpha-testing some new functionality that breaks my writing down into fiction and nonfiction. (Hint: so far, so good.) In the meantime, I’ve made my Daily Almanac script–which works with the writing tracker to produce a daily summary email–available to anyone who wants to use it. I updated the project on GitHub for anyone interested.

5. For the first time in nearly a year, I’ve done no reading for 2 consecutive days. That’s how busy I’ve been. Seriously, it has been intense.

6. Some changes to the blog are coming. Nothing too dramatic, but I am testing out some new styles. For the most part these will be subtle changes that should improve the look of the site, and take advantage of improvements to CSS and browser capabilities. The biggest change will be to my How I Became a Professional Science Fiction Writer page. That should be pretty cool, so stay-tuned for that.

7. I started watching Star Wars: The Clone Wars cartoon series. Since I’ve stated here often enough that I’ve pretty much given up television, it is only fair when I admit to slipping. The Little Man had been watching episodes, and occasionally, I’d hear one in the background while writing or doing some other activity. What struck me first was how much better they were than the last 3 movies. The writing is pretty darn good. So are the story arcs. The Little Man has just finished the first season, and I’m only on episode 6 or 7, but I am enjoying it. Usually, I’ve been watching an episode or two just before bed. On some nights, I’ve tried for more, but I’ve just been too tired lately.

I think that’s about it. Once again, sorry for not being as active here as usual. Hopefully things will return to normal soon.

Notes

  1. As with a lot writing for news and magazine outlets, I write the article, but the editor typically comes up with the title. I mention this only because Kelly said that “N00Bz” didn’t sound like a word I’d use.

The Daily Almanac Has Been Added to My Google Writing Tracker

One of the most frequent requests I get regarding my Google Writing Tracker is to make my Daily Almanac available as part of those scripts. The wait is over. Today, I pushed out the Daily Almanac the Google Writing Tracker project on GitHub.

For those who don’t know, my Google Writing Tracker is a set of script that automate the process of tracking what I write every day. Since I do all of my writing in Google Docs, these scripts run automatically each night, look at what I wrote, tally up the stats and record them in a spreadsheet. They also email me a copy of all of my writing for that day, including differences from the previous day.

Along with those scripts, I built another script that I call my Daily Almanac. This script culls that spreadsheet that is populated by my Writing Tracker scripts and gives me a summary report each night. The report tells me how much I wrote that day, and breaks it down for me. It also identifies any streaks I may have set (369 consecutive days of writing as of today) and any records I may have set. (The most words I’ve written in a day, etc.) I set up my Daily Almanac to send the nightly email to Evernote so that I have a nice record there of my day-to-day writing activity. Here is what a typical Daily Almanac entry looks like:

Daily Almanac July 23

The Daily Almanac is now available for anyone who wants to use it with the Google Writing Tracker. I have checked it in to the project on GitHub, and I’ve updated the README file with detailed steps for setting it up.

As always, this is a use-at-your-own-risk thing. I just don’t have the time to support these scripts. The best I can do is make them available for others who want to give them a try, and encourage folks to add to improve upon them. Be sure to read the instructions carefully, and if you do find any bugs, feel free to open up an issue in the GitHub project. I may not fix it any time soon, but at least it will get tracked.

Alpha Testing an Update to My Google Writing Tracker

Beginning today, I am doing some alpha testing of the first significant update to my Google Writing Tracker scripts in more than a year. I will be testing these out myself over a period of a week or two before pushing the changes to GitHub.

The newest feature is that the writing scripts now track both fiction and nonfiction writing. This may not seem like much, but it is a big deal for me, as I have been writing a lot more of the latter lately and want to be able to look at the data to see how much of what I write each day is fiction, and now much is nonfiction. Fiction and nonfiction columns are captured separately in the Writing spreadsheet, and a third column keeps track of the total writing, fiction and nonfiction.

My Daily Almanac has been modified to report on this. Here is what a new version of my Daily Almanac email looks like when it is sent to my Evernote account:

DailyAlmanacNew

The script distinguishes between fiction and nonfiction by looking for a tag I include at the end of my template document:

  • {{Fiction}} = Fiction
  • {{Nonfiction} = Nonfiction

I am also working on a few other changes:

  • I’ve added the ability to run the script in a test mode, that sends the email containing what you wrote that day, but does not actually update any values.
  • I’ve added a check to make sure that the script only looks for Google Doc files in the sandbox.
  • I’m working on simplifying the setup process.

It will probably be 2 weeks before I push these changes to GitHub. However…

I have added my Daily Almanac script to the GitHub project today because I know a lot of people were asking for that. Stay-tuned for the next post for more details.

Using RescueTime to Answer the Question: When Do I Write?

I‘ve written quite a bit about how much I write, and that I find ways to write every day. What I haven’t talked about much is when I do my writing. Remember, I have a full time day job, and two little kids, so my time is very limited. In order to write every day, I needed to adjust to the fact that I couldn’t count on a fixed time of day, or a fixed duration of time in which to write. I had to learn to write whenever the time became available.

Since early this year, I have been using RescueTime on all of my computers. For those not familiar with it, RescueTime is an application that tracks what you do on your computer and provides you with data about your productivity. RescueTime has a database of applications and websites and ranks them anywhere from Very Unproductive to Very Productive. It gives you a “productivity pulse” from 0-100 telling you how productive your days were. One of the things that RescueTime captures is when you used an application and for how long.

Yesterday, I finally got around to playing with RescueTime’s API, and was able to pull out data about my use of Google Docs, which is where I do all of my writing. I learned a lot about when I write by looking at that data. I also confirmed some things that I already knew.

When do I write each day?

I went back to March of this year and took data from March 1 through yesterday. I filtered the data to look at just the “Writing” activity in RescueTime–that is, applications that are related to writing. I further filtered those down to Google Docs to ensure that I was capturing my regular daily writing, all of which I do in Google Docs. I aggregated the data by hour to see when during the day I typically do my writing. Here is the results:

When Do I Write

You can see that the vast majority of my daily writing is done between 7-9 pm. Indeed, of the 102 hours of writing that RescueTime has logged since March, more than half–53.1 hours–has taken place between 7-9 pm.

This data aggregates all days in the date range, including weekends. I sometimes write early on Saturday or Sunday mornings, especially when I know I have a big day ahead, so there is a spike there. Also, I sometimes write when the kids nap on the weekends (something that is increasingly rare), and so you see a small spike between 1 – 3 pm as well.

If I break things down by weekday/weekend writing times, here’s how things look:

Weekday-End Writing

The pattern on weekends is roughly the same as weekdays, and yet the chart is a little deceiving because it makes it look like I write a lot less on weekends than on weekdays. But remember, there are only 2 days in a weekend, and 5 days during the workweek. From March to the present, I’ve spent 76 hours writing during the workweek. This averages out to 15.2 hours per weekday.

However, I’ve spent about 30 hours writing on weekends in that same period. This averages out to 15 hours per weekend day. Put another way, I’ve written a total of 15 hours for each day of the week in the period from March to the present. I write just as much on the weekends as I do on weekdays.

An important note on the data collection

One thing I want to emphasize here. All of the data was collected automatically by RescueTime. I did not have to log my writing time. I did not have to take any extra steps, beyond opening my document and typing. RescueTime captures it all, automatically. Indeed, there is a gap in the data. When I was on vacation in Maine, I took a laptop with me that I forgot to install RescueTime on, so none of my time that week was captured.

But the key point here is that all of this data was generated without my having to take a single action beyond doing what I normally do. Of course, I did have to spent a few minutes creating the charts for this post, but the data was already there. I just had to grab it and process it. This, in my opinion, is a vital element to consistent tracking. If I had to take steps to log my time each time I was writing; if I had to “clock-in” and “clock-out” I would never have collected the data in the first place.

No Going Paperless Post This Week

I am under the gun on a couple of projects at the day job that have tight deadlines. I am also under the gun for some writing-related projects. To give me a little breathing room, I’m going to take this week off from the Going Paperless post. Part 2 of my 2-part series, How I Simplified My Note Organization in Evernote will come on next Tuesday, July 29.

Sorry for the delay. In the meantime, if you haven’t checked out Part 1 yet, you can find it here. And, of course, there are more than 110 other Going Paperless posts that I’ve written.

365 Consecutive Days of Writing

365 Days of Writing
Click to enlarge
This evening, I wrote nearly 1,900 words, and in doing so, achieved a major milestone. I have now written for 365 consecutive days. That’s one full year. The last day on which I did no writing was July 21, 2013, the day I traveled home from the Launch Pad Astronomy workshop. Since that day, I have written every day, to the tune of 344,000 words. Over the course of the last 365 days I have averaged 943 words per day. That is roughly 40 minutes of writing per day, or a grand total of about 243 hours spent writing.

On my best day in the last year, I wrote more than 5,300 words. On my worst day, I barely scratched out 70. But I have written every day.

This streak, while significant, is part of a larger effort to write every single day. Since I started on this adventure, I have now written 508 out of the last 510 days.  That’s not too shabby.

The chart above shows the last 365 days. You can click it to see a larger version. It’s interesting to note a few patterns in the data. The one that jumps out at me the most is how my 7-day moving average fell during the cold winter months. Also, on 8 separate occasions, I’ve exceeded 3,000 words in a single day.

As you might expect, I’m pretty happy today!

Silence in the Library / Forest of the Dead

Kelly has been watching Doctor Who. She watches an episode or two each evening. Usually I am writing or reading while she is doing this, but occasionally, I’ll get sucked into an episode. It’s rare, but it happens. It has, however, happened the last two nights in a row. She watched an episode called “Silence in the Library” and I was vaguely reminded of Audrey Niffennegger’s The Time Traveler’s Wife. It was a fascinating episode, really. And it ended with a “To be continued…” cliff-hanger.

So last night, she watched the concluding episode, called “Forest of the Dead,” and once again, I was sucked in. But I liked it. In fact, the double-episode quickly rose to the top of my favorite of the small handful of episodes that I’ve seen, eclipsing “Blink,” which was the first episode I ever watched, after a crowd-sourced recommendation. The ending of “Forest of the Dead” was spectacular.

Now, before anyone jumps into say, “Oh, you have to watch episode x, or y, or even z!” understand that this was a fluke. As much as I liked the episode, I just don’t have time for TV. Unless I really need to give my brain a rest, the time I spend watching TV is time that I could be writing. It’s not that I don’t like what I see. It’s that I like writing more.

Well, also, with rare exception like this double-episode, I can’t really stomach TV dramas anymore.

In any case, I thought I should at least mention that I saw and enjoyed both these episodes of Doctor Who since there are people out there who can’t believe that, as a science fiction writer, I don’t watch the show regularly.