Hugh Howey is the author of WOOL, one of my favorite sci fi series. His essay Your Fear is My Opportunity is a rant on Amazon and self-publishing, and I really appreciate his perspective as someone who has gone through the hard process of self-publishing:

The things I advocate for: Reasonably priced e-books, for publishers to take risks and do exciting things, for us to embrace the future of storytelling and allow it to coexist with the past, to release all editions of a work at once, to get rid of DRM, to mix up genres and do something fresh and new … these are all things I’ve wanted as a reader for longer than I’ve been writing.

And this:

I am a reader first. And I want more readers. Selfishly, as a reader, I want more readers. I want to see airports full of people staring at books, e-readers, and tablets laced with text. Not people staring at cell phones, Candy Crush, Facebook, or authors’ blogs. I want book culture everywhere. I want interactions with strangers to be about what they’ve read lately. I want my social media feed to be all about books. I’m an addict, and I want to get other people hooked. Maybe that’s a bad thing. I don’t care.

If you haven’t read WOOL you should give it a try. Great storytelling whether you’re a sci fi fan or not.

Clive Thompson’s “I can’t even” is easily my favorite essay of the week. Clive goes back 100 years and finds an author that excelled at… well, I’ll let him tell you:

It must be said: Lovecraft is not a great literary stylist. His prose is good, but not great.

The one exception? This linguistic subgenre—the craft of finding new ways to say that he can’t say something. When Lovecraft does describe a monster straightforwardly, he often stumbles, defaulting to pretty journeyman prose. But when he describes the way a monster can’t be described? He is endlessly inventive. I read and reread my collection of Lovecraft, slapping in a Post-It Note whenever I hit upon one of these I-can’t-even moments, and soon the book was crammed with stickies. I’m starting to believe these catchphrases may be his most enduring contribution to English letters.

My favorite example?

The frantic playing had become a blind, mechanical, unrecognizable orgy that no pen could ever suggest.

Masterful. Even better than my go-to “I can’t even” gif:

I don’t know if I’ve always wanted to write a book, but I do know that I’ve been writing the one I’m announcing today in my head for many, many years. It’s called Making It Right: Product Management For A Startup World, and it’s my attempt at putting together a practical framework for building great products:

The book came about because I saw a lot of people in organizations perform some of the activities that make up the role of product management. The problem is that very few people take a holistic view of the product, and this is not a role that should be split up into tiny pieces. So, you see marketing people doing some design and research, business analysts doing some spec writing, developers managing the product backlog, and so on.

All this without a person who is responsible for the overall vision, prioritization, and execution of the product. With this book I wanted to provide a complete product strategy that is agnostic to whatever development process people use (agile, etc.).

So here are a couple of links to check out more detail, if you’re interested:

• Smashing Magazine has a launch post up today.
• You can buy it directly from Smashing for $10 in their digital store.
• For the next couple of days, you’ll also be able to buy it for 99c on Amazon.

Smashing tells me that the Amazon thing, in particular, is important for the first couple of days after launch. So if you’re so inclined, please pick it up for 99c, and write a review. It will really, really help to give us a good launch.

Huge thanks to the Smashing Magazine team, and my technical editor Francisco Inchauste. They’re my heroes. And now I have to lie down.

The AP is increasingly starting to use software with no human intervention to write basic news stories, but Kevin Roose says that we shouldn’t be alarmed about it. From his article Why Robot Journalism Is Great for Journalists:

Robot assistance may even spur human reporters to do our jobs better. With software producing the equivalent of old-school “clip files” for us, we’ll essentially have full-time research assistants. The information in our stories will be more accurate, since it will come directly from data feeds and not from human copying and pasting, and we’ll have to issue fewer corrections for messing things up. Plus, with our nuts-and-bolts reporting out of the way, we’ll be able to focus on the kinds of stories that educate and entertain readers in a deep way, rather than just dragging simple information from Point A to Point B.

I don’t quite know how to describe Peter Richardson’s The Lay of the Land. It’s about topography, maps, and cartoons, but actually about how we see the world:

Eventually I escaped my fjord, but a few lessons of my youth have been repeatedly confirmed: topography is important, and there’s no faster way to make an impression than with a cartoon. And by “cartoon” I mean a simplification which exaggerates some details and omits others. You could also say “model,” but I like the connotations of “cartoon”; it retains a transgressive frisson that the word “model” doesn’t have, unless you’re in fashion. But anyway.

Great essay — a bit rambling, but in a way that keeps you engaged.

I have no idea if anyone else will find this helpful, but I’m so excited about it that I have to share it1. One of the most time-consuming and repetitive tasks in blogging is uploading images to my Amazon S3 account, generating the CDN link, and inserting it into the post. But I’ve now cobbled together a recipe that makes this really easy, and I’d like to tell you about it. First, here are the ingredients you’ll need:

1. An Amazon S3 account for image storage (optional: Cloudfront CDN)
2. TextExpander to handle the repetitive typing
3. Hazel to automate the upload to S3
4. Dropbox isn’t technically necessary, but it makes everything just a little bit smoother.

With that said, here are the steps in the recipe:

Step 1: Set up a Hazel workflow to upload new files to S3

First, we need to set up Hazel to watch a folder and upload any new files to your S3 bucket. The Macdrifter article Upload to Amazon S3 from Dropbox using Hazel is extremely helpful for this. I basically copied that script with some minor adjustments. Here’s what it looks like:

Note that you have to change the type of shell script you run to /usr/bin/python. The script I use looks as follows (again, see the Macdrifter article for the whole story):

import boto
from boto.s3.connection import S3Connection
import os
import sys
import urllib
from datetime import date, datetime
import subprocess

# This is how Hazel passes in the file path
hazelFilePath = sys.argv[1]

# Obviously, you'll need your own keys
aws_key = 'YOUR_KEY'
aws_secret = 'YOUR_SECRET'

# This is where I store my log file for these links. It's a Dropbox file in my NVAlt notes folder
logFilePath = "/Users/~YOUR_COMPUTER_NAME/Dropbox/Notational/Link_Log.txt"
nowTime = str(datetime.now())

# Method to add to clipboard
def setClipboardData(data):
    p = subprocess.Popen(['pbcopy'], stdin=subprocess.PIPE)
    p.stdin.write(data)
    p.stdin.close()
    retcode = p.wait()

# This is the method that does all of the uploading and writing to the log file.
# The method is generic enough to work with any S3 bucket that is passed.
def uploadToS3(localFilePath, S3Bucket):
  fileName = os.path.basename(localFilePath)

# Determine the current month and year to create the upload path
    today = date.today()
    datePath = today.strftime("/%Y/%m/")

# Create the URL for the image (Add your own path here)
    imageLink = 'https://cdn.elezea.com/images/'+urllib.quote(fileName)

# Connect to S3
    s3 = S3Connection(aws_key, aws_secret)
   bucket = s3.get_bucket(S3Bucket)
   key = bucket.new_key('images/'+fileName)
   key.set_contents_from_filename(localFilePath)
   key.set_acl('public-read')
   logfile = open(logFilePath, "a")

try:
       # %% encode the file name and append the URL to the log file
       logfile.write(nowTime+'  '+imageLink+'n')
      setClipboardData(imageLink)
   finally:
      logfile.close()

Here’s what the script does in my case: Whenever I add a new file to the Img folder in Dropbox, it uploads the file to S3, copies the URL to the clipboard, and also adds that URL to a Link_Log text file in my nvALT folder for later access if needed (or if I add multiple images in one go).

Step 2: Set up TextExpander shortcuts

Once the image is added to S3, the rest is handled with TextExpander. When I want to add an image to a blog post I type:

,img

That expands to:

<p><img style="display: block; margin-left: auto; margin-right: auto;" title="%fill:image title%" src="%|%fill:image source%" border="0" alt="%fill:image title%" /></p>

It asks me to give the image an alt tag, and then it places the cursor where I’m going to add the source file. Since the source URL is already in my clipboard, I then just ⌘-V and I’m all set.

They call it magic

That’s it. It might seem like a lot of work, but now that everything is set up my workflow is extremely simple:

1. Add new image to the Img folder
2. Type the TextExpander shortcut and paste the Image URL where I want the image to appear

I think it’s going to save me at least as much time this year as it took to write this blog post.

Oh. Wait.

---

1. It also gives me an opportunity to pretend I’m Dr. Drang, but I digress. ↩

In A Corrected History of the Typo Adrienne LaFrance argues that maybe print errors aren’t such a bad thing:

What we’ve lost, in many cases, online, isn’t the integrity of print, but the traceability of its weaknesses. Centuries ago, “errata lists became, paradoxically, markers of well-made books.” The made in “well-made” is a key word here. Mistakes can serve as reminders that books are made at all—the physicality of the process, the “connection between the book going wrong, momentarily, and a sense of the process of production being briefly revealed, or implied,” as Smyth put it in a recent paper about print in Early Modern England. It’s why readers relish newspaper typos—they represent the lifting of a veil, and hint at the human (and that human’s fallibility) on the other end of the object. 

If this kind of thing is of interest to you, it reminds me of post I wrote a couple of years ago called The unnecessary fear of digital perfection. It cites a bunch of articles that lament the fact that we don’t let ourselves make mistakes any more.

David Carr in For Email Newsletters, a Death Greatly Exaggerated:

Email newsletters, an old-school artifact of the web that was supposed to die along with dial-up connections, are not only still around, but very much on the march. […]

And:

Email is a 40-year-old technology that is not going away for very good reasons — it’s the cockroach of the Internet.

Well, I confess that I have also succumbed to the lure of this particular cockroach, and have been experimenting with a revamped newsletter. If you’re keen, join in…

In Punctuated Equilibrium Joe Pinsker reports on an atrocity that doesn’t get nearly enough press — the death of the apostrophe:

A battle is being waged over the apostrophe, and the names of two of the online factions—the Apostrophe Protection Society and Kill the Apostrophe—suggest an extremism usually reserved for blood, rather than ink or pixels. The former, founded by a retired British copy editor, provides a gentle guide to deploying the apostrophe. “It is indeed a threatened species!” the site warns, a little preciously. The Web site Kill the Apostrophe, meanwhile, argues that the mark “serves only to annoy those who know how it is supposed to be used and to confuse those who dont.”

This important article comes hot on the heels of a report on another alarming trend. A recent poll discovered that 43% of Americans don’t believe in the Oxford comma.

We should all know this by now, but just a reminder — this is why the Oxford comma is important:

Image source

Rob Horning’s Me Meme is not an easy read, but it’s worth the investment. He doesn’t waste time with a fluffy intro, he just jumps straight in:

With social media, the compelling opportunities for self-expression outstrip the supply of things we have to confidently say about ourselves. The demand for self-expression overwhelms what we might dredge up from “inside.” So the “self” being expressed has to be posited elsewhere: We start to borrow from the network, from imagined future selves, from the media in which we can now constitute ourselves.

There are too many great quotes in here to choose from, so I’ll go with one more and then just encourage you to read the whole thing:

We shift from consumerist pleasures of fantasizing about how owning certain branded goods would make us into a certain kind of person and secure us a certain sort of affirmation to fantasizing about triumphant moments of social quantification, about getting likes and retweets, having lots of Tumblr activity, etc. […] Without viral content, you are in danger of becoming a blank.