Policy on Product Reviews and Plugs

For some reason, I have been getting 3 or 4 requests per day to review some productivity product, service, or website. The requests are almost all extremely polite, professional, and the products almost always interesting. But with so many requests coming it, I figured it was time that I put up a post that I could point people to about my policy on product reviews and plugs. If you are not interested in this, you can stop reading now. If I’ve directed you here, please continue.

For the vast majority of the requests I get to review or plug a product, the answer, I’m afraid, is no. Why?

1. Time. I have a very limited supply of time, and like everyone, that supply dwindles with each passing day. After family, and the day job, my main priority, as far as time goes, is my writing. My writing almost always eats up the remaining time I’d have to do things like reviews products. I won’t review or plug something I haven’t had the time to investigate thoroughly, and I rarely have the time do that these days.

2. I am not a product reviewer. Let’s face it, my job is not reviewing products. I am a software developer by day, and writer and blogger by night. Strictly speaking, product reviewer is not in my job description.

For over a year, I had a book review column at InterGalactic Medicine Show, where I’d review a book per month on average. That was a paid writing gig, but I have it up because it was eating into my writing time too much. Bottom line: while I do write the occasional odd review, I don’t particularly enjoy that work, and would prefer to spend my time writing other things.

3. But you do occasionally review products. On occasion, I’ll review something here on the blog that I find interesting. Usually, it is something that I have been using myself long enough (and happily enough) that I think a review is worthwhile. These reviews are almost always written without a request. That is, no one is asking to write them. I’m writing them because I found something useful on my own. I can count on one hand the number of times over the last few years when I have reviewed something that someone asked me to reviews.

4. Ah, but what about Evernote, aren’t you their paperless ambassador? Yes, I am. But if you go back through the history (all of which is documented here on the blog), I was writing about how I used Evernote on my own before Evernote approached me and asked me to join their ambassador program. I should also point out that being an Evernote ambassador is not paid gig. They give me complementary Evernote Business account and that is something I would be perfectly willing to pay for myself.

5. So then what does it take for you to review and/or plug a product? Most products I have reviewed have been things I have found on my own. They are things in which I see a clear and obvious benefit over my current way of doing things. Let me emphasize that the benefit is clear and obvious to me. In almost every case, the product simplifies or automates something I was doing manually before. Some examples:

  • My FitBit made it painless to track my activity.
  • My Automatic Link made it painless and effortless to track my driving and mileage.
  • My Fujitsu ScanSnap s1300i made it effortless to scan documents to Evernote
  • Gina Trapani’s todo.txt made is easy for me to manage my to-do list in the way that I want to work.
  • RescueTime made it painless for me to track where and how I spend my time on the computer.
  • CrashPlan made it painless and effortless to ensure my data is backed up.

Consider that it takes time to test out a product, time to switch to a product, and more time to integrate a new product or service into your system. Only those that make these painless and simple, and have a clear and obvious benefit over what I am currently doing are potential candidates for a review.

Recent Interviews and Guest Posts

Since I haven’t had a chance to note it here specifically, I’ve recently participated in an interview and a guest post that folks might be interested in.

Interview at AlphaEfficiency Magazine

The good folks at AlphaEfficiency magazine recently interviewed me about quantified-self and productivity. It was a fun interview to do, and I think there’s some good stuff in there for folks interested in (a) how quantified self data can be used in a practical way, and (b) how to get started.

 

Part of the interview is available online, but to read the whole thing, you need to grab a copy of the magazine.

Guest post at the Write Life blog

This morning, I have a guest post at the Write Life Blog where I talk about 5 mistakes I’ve made in my writing career (not the only five) and what I have learned from them. You can head over to the Write Life blog to read “Writing Advice: 5 Things I Wish I Could Tell My 20-Year-Old Self.”

On the Value of Practice

Once upon a time, I couldn’t read. I practiced sounding out the words, and each day seemed like I was making no progress. Then one day, I could read–haltingly, but I could read.

Once upon a time, I couldn’t write a line of code. I’d see these long elaborate programs listed in the early computer magazines and wondered how people figured this stuff out. I practiced, and practiced, and one day, I wrote a simple program. And then another, and the programs got more complex, and the languages changed, and I get better and better at it. Today, I make a living a software developer.

Once upon a time, I couldn’t fly. Then I took flying lessons. I practiced as much as I could. I passed my written, and then my oral test, and finally, my practical test, and came home from the airport that day with a private pilot’s license in my pocket.

Once upon a time, I couldn’t write. My stories had no identifiable beginning, middle, or end. They- characters were carved out of thin cardboard. The language was in primary colors. The dialog dripped adverbs. The plot was an overly complicated Rube Goldberg contraption. I practiced. I read a lot. But I practiced a lot. I tried to learn from my mistakes when that was possible. I sold a story, and then another, and then another, and then more.

Without practice–a heck of lot it in my case–I would never have learned to read, or write code, or fly a plane, or tell stories that at least a small number of people seem to enjoy. If there has been any overarching lesson in my life, it has been this: don’t underestimate the value of practice.

2 Years of Writing

It crept up on my, but I awoke this morning with a feeling that the date, February 27, was vaguely familiar. I couldn’t quite place at, not at first, and then around mid-morning, it hit me. It was 2 years ago today that I began my efforts to write every day. It was also 2 years ago today when I first started to use my Google Docs Writing Tracker.

2 years of writing

Prior to February 27, 2013, I’d tried on a number of occasions to start a streak where I wrote every day. I was never successful. However, in the 2 years that have now elapsed since February 27, 2013, I have written every day, except for 2; that’s 728 days out of the last 730. What’s more, I haven’t missed a day since July 21, 2013. As of today, I’ve written for 586 consecutive days.

How’d I do it? Well, I’ve talked about here and here, so I won’t rehash it all in this post. But I do want to point out once again the cumulative effect of writing a little bit every day. In the last 2 years, I have written a total of 631,960 words. I’ve averaged 865 words/day, which for me amounts to about 35 minutes per day. I’ve sold around 15 stories and articles during that time.

For me, the most important thing is practice. I’m a believer in Stephen King’s advice that to be a good writer, you need to read a lot and write a lot. Every bit of writing I do is practice. I make mistakes, and I try to learn from them, and hopefully, as with all practice, it is making me a better writer.

Another Snow Day

Another snow day

The snow began falling sometime around 2 or 3 am. By the time we woke up to start the day, schools had been closed, which made the kids happy. My office is open, but the roads are treacherous, and besides, the kids are home and they require our attention, so it is another snow day for everyone. On tap for today:

  • Finish reading the current issue of Wired.
  • Start on the current issue of Smithsonian.
  • Get through more of ‘Salem’s Lot.
  • Final touches to the new story based on beta-reader feedback.
  • Possibly start another new story.
  • Stay warm.

All of this, of course, in between keeping the kids entertained. Remember those days when it was possible to do just one thing at a time? Did those days ever really exist?

28 Days of Crazy Busy

I just punted on my Feedly list.

2,469 posts had accumulated, and I had to face the fact that there was no way I was going to catch up. So I punted. I skimmed the list, sent a few items that caught my eye to Pocket, and marked the rest as read and moved on. Full reset.

That digital footprint, however, provided an interesting insight into how long I’ve been crazy busy with the day job lately. Usually, I skim Feedly at least once a day, and either send to Pocket the stuff I want to read later, or clear it out, so that each day starts more-or-less fresh. When I looked at Feedly this morning, however, I saw that the last time I had cleared it out–the last time I had really looked at it in earnest, was 28 days ago. I’ve been so busy that not only have I not had time to read the articles in Feedly, but I haven’t even had time to review or clear them out.

Well, it’s done now, and I’m back to a clean slate, although I did so essentially by “rebooting.” I shudder to think of all of the good posts I’ve missed sin simply skimmed the 2,400+ pieces that had accumulated in that time.

High Word Count Days

As a counterpoint to my earlier post on low word count days, let me take a moment to discuss high word count days. And specifically, in the context of yesterday’s writing, where I managed to blow away my previous one-day record of 5,300 words by writing nearly 7,200 words. If you are not a writer, 7,200 words might not mean much so let me put it into perspective: it’s about 30 double-spaces pages.

Most full time writers I know consider 2,000 words a full day’s work. Since I am not a full time writer, I consider 2,000 words or better a high word count day. How many of these high word count days have I had in the last 728 days? 26 of them, making them twice as rare as a low word count day. Here are all of my high word count days laid out over time:

High word count days

Put another way: I have a low word count day (less than 250 words) about once every 13 days. I have a high word count day (2,000 words or more) about once every 28 days. I think this makes sense. Given limited time, it’s easier to squeeze in less than a page, then it is to find the time to write ten pages.

I took the low word count days and high word count days and mashed them together, and here is what I got (low = red, high = blue):

Low-High Mashup

All the white space in between are days on which I wrote at least 250 words, but less than 2,000 words.

Perhaps the most interesting thing to come out of this exercise is to find that a high word count day does not necessarily follow a low word count day. This might be true if I were trying to make quota, but since my only real goal is to write every day, I don’t feel the need to “make up the difference” after a low word count day.

Yesterday’s record was an oddity all around. I had written about 3,000 words of a first draft of a story, and yesterday, the rest of the story just kind of clicked. I wrote the remain 3,000 words almost without stopping. As I have explained before, my first drafts are for me–me telling myself the story. My second drafts are complete rewrites. Now that I know the story, I can tell it to an audience, adding all kinds of nice embellishments. But it means that I rewrite the whole thing. So I started the second draft yesterday as well, and managed to get through about 4,000 words of it before calling it quits. Thus,a 7,200-word day.

Interestingly, the more I wrote, the more I wanted to write. Writing does not tire me out the way that, say, spending 8 hours writing code does. I get mentally drained from coding, but I seem to derive an endless supply of energy from writing. Whether or not the writing is good… well, I guess my beta-readers will let me know.

In any case, I suspect it will be a very long time before I have another 7,000 word day.

There was a time when I thought I would never be published…

Once upon a time, when I first started to write with the idea to sell stories, I used to have these wild daydreams of being published. I’d finish writing a terrible short story and then sit back in my chair and imagine what it would be like just to be published, to have written something good enough that an editor was willing to pay money for it, and that readers other than my friends and family would read.

My reverie was a lot of like those silly daydreams of winning the lottery. I’d come home from class one day, and find an envelope in the mailbox. Instead of a form rejection slip, the envelope would contain a Letter of Acceptance. I had no idea what such a letter would look like, but there it was. I’d dance around the room, happy as can be, floating on the thought that I’d done it! I was a published writer.

Then I’d come back to reality, face the blank page, and wonder if it really wasn’t just a pipe dream.

One day, I sold a story. I was thrilled. A contract arrived in the mail, followed by a check, and a few months later, my first published story appeared in an online magazine. It was wonderful, delightful, and very much like winning the lottery. In the back of my mind, however, I wondered if I would ever be published in one of the big genre magazines, especially Analog, which had been around since the 1930s, and in which many of my heroes had been published.

I thought that it probably wouldn’t happen. The stories published there were just too good, the competition for space too fierce. This didn’t deter me from writing, it simply provided a new form of daydream. I’d been published, and now I would close my eyes and imagine what it would be like to be published by Analog, my name of the table of contents, my byline on a story in the pages of that revered (well, by me, anyway) magazine. No, I didn’t think it would happen, but it was fun to daydream about. And I kept writing.

Then, one day, I sold a story to Analog. I couldn’t believe it. I was thrilled, but I was sure it was a one-time thing. I kept writing. Analog bought more stories and articles from me. So did other magazines. So did some original anthologies.

These days, I don’t worry much about selling stories. In most cases, when I write a short story, I’m pretty sure I will sell it, eventually. But I’ve been writing longer and longer pieces. I’ve written a novella, and a first draft of a novel. My daydreams no longer deal in short fiction. I’ll tilt my head back, close my eyes, and imagine I’ve just gotten word that I’ve sold a novel. I can almost see it. I can almost imagine how exciting that would be. An entire book that I wrote, appearing in bookstores throughout the country. How cool would that be? Just thinking about it gets me giddy.

My tendency is to think that it probably won’t happen. Writing a novel is hard. Writing good novel is really hard. The competition is fierce, and there are lots and lots of good novels being published every week. Mine would just be static within the noise. On the other hand…

I never thought I’d really sell a story. And when I did, I never thought I’d sell a story to Analog. And when I did that, I never thought I’d do it again. But of course, I did. And so I no longer worry much about the self-doubt that I face as a writer, because while the doubt is always there, lingering in the shadows, waiting for a weak moment to pounce, I’ve shown myself that, despite the doubt, I’ve managed to achieve more with my writing than I thought possible. So why not a novel? Why not bestseller? Why not a life as full time writer? Ah, one can dream.

But one can also write.

Low Word Count Days

Yesterday, I managed to write only 112 words on the story that I am currently working on. It is the lowest word count I’ve had since April 11, 2014. I thought I should mention it here since I often talk about my writing streak and my daily averages, to show that sometimes, even the best laid plan of mice and keyboards make it hard to fit in the day’s writing. Yesterday was one of those days.

112 words does not sound like much at all. Even so, I spent 20 minutes coming up with those 112 words, and they represent a complete scene in the story. I knew that yesterday was going to be a long day. I had a lot of work to focus on at the day job. In the evening, we went out to dinner with friends. So there wasn’t going to be much time to write. I squeezed in the 112 words early in the day, thinking I might have a chance to come back to add more later, but that didn’t happen.

I’m okay with that. Even though it was only a few short paragraphs, I felt good about what I’d written, and I was relieved that I’d gotten it done early in the day, rather than stress it about not having it done yet through the latter part of the day. For me, the goal is to write every day. It doesn’t matter how much or how little.

But it did make me curious about how often I have these particularly low word counts. Since one full manuscript page is about 250 words, give or take, I’ll use 250 words as a threshold, and ask: how often have I written less than a page a day?

In the last 724 days, I have written less than a page 57 times. That’s about 7.8% of the time, or about 1 out of every 13 days. Looking at it as a timeline, my low word count days look as follows:

Low word count days

I’ve learned not to be discouraged about low word count days. Some writing is better than no writing, even if it’s a page or less on a given day.

But mostly, I wanted to show that despite my growing consecutive day writing streak, not every day is an 800 or 1,000-word day. There are plenty of days (57 day of them!) when I can barely get a page.

 

The Little Man and the Brown Marmorated Stink Bug

I was in the shower when the Little Man let out a shriek that would raise the dead. He had been sitting on our bed, watching Power Rangers Megaforce when a bug that had been crawling along the wall landed on his knee.

Little man, meet Halyomorpha halys; brown marmorated stink bug, meet the Little Man.

After he calmed down (his jets had launched him well beyond the orbit of the moon), he asked what it was. “A stink bug,” I told him. You’d think a five year old would instantly fall in love with anything that had the word “stink” in it. Perhaps I should have called it a fart bug.

It was really a minor thing, except the Little Man now worried that Mr. Halys might somehow find his way into his room, and worse yet, into his bed. Kelly tried to assuage this by giving the bug an exciting ride down the toilet. This seemed fine for a little while. Then, after the Little Man used the facilities, he said, “Daddy, we have to make sure to close all of the toilets in the house to make sure that the bug doesn’t come up.” We made sure all of the toilet lids were closed. Stephen King, eat your heart out.

Once in bed, the worry crept in that this bug would somehow come back, and bring its legions with it.

“I’ve got it covered,” I told the Little Man, “Zekie (our cat) will patrol up here tonight.”

“What will he do?”

“Well, if he see the bug, he’ll eat it.”

He’ll eat it?” the Little Man said, shocked.

“What’s your favorite food in the whole world?” I asked him.

“Candy.” Of course.

“Well, for cats, stink bugs are like candy.”

“Not uh,” he said.

“What happens when you eat too much candy?” I asked.

“You get a tummy ache.”

“And don’t we come home sometimes to find that Zekie has been sick on the floor?”

“Yes.”

“Well, what you do think made him sick?”

That seemed to make him feel better. I tucked him in, gave him kiss, turned off the light. His brow furrowed, “But Daddy, how will Zekie see the bug in the dark?”

Stop obsessing over the bug, I wanted to say, you’ll give yourself nightmares for no reason. “Well, Zeke is cat, and cats are nocturnal. Do you know what nocturnal means?”

He nodded, “It means that they don’t sleep at night, and can see in the dark.”

“There you go.”

He considered this logic for a long time, and then seemed satisfied. “Okay, Daddy,” he said, “just make sure you bring Zeke upstairs right now, okay?”

“Okay,” I said.

The Little Man slept soundly through the night.

His father, on the other hand, had dreams of stink bugs swarming his bed, crawling all over him, and getting in between the keys of his keyboard, making it particularly difficult to write.

How Do You Find Time to Write?

From time-to-time, I get asked how I find the time to write. I supposed this is, in part, because of my consecutive-day writing streak (which now stands at 576 days). But I think part of it comes from the fact that I manage to write while working a full time job, while blogging, and while raising a family. The question comes in various forms but it all boils down to the same thing: how do you find time to write?

I’ve talked about this before, but I don’t think I’ve ever written a post on it exclusively (I could be wrong–with more than 6,000 posts it’s hard to remember everything I’ve written). So I thought I’d try to answer this question here. Keep in mind that the question I am answering is how do find time to write. Your mileage may vary.

1. I challenged my assumptions about the time I needed to write

When I started to write every day, nearly two years ago now1, the first thing I did was test my assumptions of what I needed to write.

With respect to time, I used to think that I needed a chunk of time–a minimum of, say, 1 hour, better yet 2 hours–to get any decent writing done. In the past, I’d tried to carve out an hour or two during the day to write. Usually it was very early in the morning, and while it worked for a time, it eventually failed. It fail for several reasons:

  1. I might be able to get up at 4 am a few day a week to get in some writing, but the long days wore on my, and eventually, I’d fail.
  2. When I did fail, I felt guilty for the rest of the day.
  3. Failure one day led to failure another day.

So the first thing I did in February 2013 was challenge my assumption about how much time I needed to write. I decided to experiment. My experiment was as follows:

  1. I would write every day, even if it was only for a few minutes.
  2. I would not schedule a specific time to write, but writing would be a priority for any spare time that I found.

This experiment required that I be able to write from anywhere, which is why, beginning in February 2013, I moved my entire writing infrastructure into Google Docs. Using Google Docs meant I could write from any device, wherever I happened to be. It meant I didn’t have to worry about moving files back and forth across devices. That meant I could spend what little time I had writing instead of copying files and managing versions.

2. I challenged my assumptions about the environment I needed to write

I used to think I needed a quiet, secluded environment where I could do my writing. But if I had to write whenever the time was available, as opposed to setting aside blocks of time, then I needed to challenge my assumptions about the environment I needed to work in.

I decided to try to write in whatever environment I found myself in, so long as the time was available. If that meant writing at the library, fine. If that meant writing in the quiet of my home office, fine. If that meant writing in the family room, with the TV blaring and the kids running around screaming, fine.

3. I collected data about my behavior in order to provide a baseline

I wrote a set of scripts for Google Docs that automated the tracking of my writing. This meant I could focus on writing, rather than tracking, but still collect the data I was looking for (how much I was writing each day). I also began using a tool called RescueTime which tracks how much time you spend on various applications and documents across your computers. This gave me real numbers for how much time I was spending writing each day, which I could use to see if my assumptions were good or not.

4. I wrote every day

With my challenges to my assumptions, and my automated scripts and data collection, I started to write. I wrote every day. Sometimes I’d only write for 10 minutes. Other times, I’d find 3 hours to write. Sometimes I was exhausted, but wrote for 15 minutes anyway. Sometimes, I knew what I was writing was terrible, but that the practice was important, so I kept at it.

Sometimes my day got thrown off. I adjusted as best as I could. When I knew my schedule would be crazy in advance, I’d plan ahead, and try to get a little writing in early in the day. At least then, it was done. If there turned out be time to do more later, I’d do more.

I found that over the course of 721 days, there were only 2 days that I could not manage to get any writing in. Both were unusually long, busy travel or conference days. I learned lessons from both, and haven’t missed a day of writing since July 21, 2013.


What the numbers told me

Over the course of my 576 consecutive day writing streak, I’ve written over half a million words, and sold 11 stories or articles. Here is what the data looks like for the duration of my streak so far:

Continue reading How Do You Find Time to Write?

  1. Although my consecutive writing streak stands at 576 days, there is a larger overall “streak” beginning late February 2013 during which I have only missed 2 days of writing. That is, I have written on 719 out of the last 721 days, the last 576 of them consecutively.

Stephen King Revisited

I have been having a lot of fun following along on Richard Chizmar1‘s Stephen King Revisited blog, as he attempts to re-read every Stephen King book in chronological order. After each book, he posts an article, as there usually several others as well looking at the work through various contexts. It’s been great fun, and as I might have expected, it’s made me want to follow along in a more literal sense–by doing this myself.

I waffled over this for several weeks, and finally decided to give a try. Chizmar is already on King’s 4th book, Rage, a book that is no longer in print, and one of the few King books I don’t already own in one form or another. So I have some catching up to do. I started re-reading Carrie yesterday, and found it to be completely enjoyable. Yes, I am reading stuff I’ve already read, but I’m having fun doing it.

I’m not planning on posting the kind of detailed essays and articles that Chizmar is doing on his site, although I may comment over there from time-to-time. And I’ll probably write about those books that I haven’t read before. Like Rage, which I ordered, used a few days ago, and which is scheduled to arrive in the mail sometime today.

I’m also trying to figure out a way to post my progress for those who are curious. More than likely, I’ll have a link on this site that you can go to see my overall progress. Stay-tuned for more on that.

Even if you are not revisiting Stephen King yourself, I’d encourage you to check out Chizmar’s Stephen King Revisited site, if you are at all interested in King’s work.

ETA (1:00 pm): The mailman delivered The Bachman Books, which includes Rage a little while ago. So I am all set for a long time.

  1. Publisher of Cemetery Dance.