A couple of articles about work and technology caught my eye this week. First, Claire Cain Miller describes how Technology, Aided by Recession, Is Polarizing the Work World:

[A new working paper from the National Bureau of Economic Research], which analyzed data from the Current Population Survey from 1976 to 2012, illustrates that the recession had a disproportionately large effect on routine jobs, and greatly sped up their loss. That is probably because even if a new technology is cheaper and more efficient than a human laborer, bosses are unlikely to fire employees and replace them with computers when times are good. The recession, however, gave them a motive. And the people who lost those jobs are generally unable to find new ones, said Henry E. Siu, an associate professor at the University of British Columbia and an author of the study.

Now, combine that problem in the mid-paying job market with an issue Thomas B. Edsall pointed out a few weeks ago in The Downward Ramp:

Just one example: the drying up of cognitively demanding jobs is having a cascade effect. College graduates are forced to take jobs beneath their level of educational training, moving into clerical and service positions instead of into finance and high tech.

This cascade eliminates opportunities for those without college degrees who would otherwise fill those service and clerical jobs. These displaced workers are then forced to take even less demanding, less well-paying jobs, in a process that pushes everyone down. At the bottom, the unskilled are pushed out of the job market altogether.

So, college graduates are pushed into mid-paying jobs, and those jobs are being replaced by technology. Not good.

Meanwhile, in opposite world, Louise Aronson writes about The Future of Robot Caregivers (if you’re counting, that’s three for three on the New York Times):

We do not have anywhere near enough human caregivers for the growing number of older Americans.

Zeynep Tufekci’s excessively titled Failing the Third Machine Age: When Robots Come for Grandma is a good critique of that piece:

Let me explain. When people confidently announce that once robots come for our jobs, we’ll find something else to do like we always did, they are drawing from a very short history. The truth is, there’s only been one-and-a-three-quarters of a machine age—we are close to concluding the second one—we are moving into the third one.

And there is probably no fourth one.

Humans have only so many “irreplaceable” skills, and the idea that we’ll just keep outrunning the machines, skill-wise, is a folly.

Put all these pieces together and you get a very scary vision of the future of jobs. The good news — I think — is that job != work.

The future of jobs might be bleak, but the future of work certainly isn’t. Technology might be taking our jobs, but it’s also giving us new ways to be creative. To be entrepreneurs. To work. As programs like Girls Who Code continue to grow, I’m increasingly optimistic about my daughters’ futures. They might not get a “regular” job one day. But my role as a parent is not to prepare them for a job anyway. It’s to foster in them the tenacity and grit to learn how to think big and make things. I’m excited about that.

Trevor Connolly breaks down the myth that the Post-PSD Era means that graphic designers will soon be out of a job if they don’t learn to code. From The Post PSD Era doesn’t want to kill designers:

Designers are more important in today’s digital world than ever. You are still responsible for creating flexible design systems and finding the styles that will connect with the user. Now you just have to do it faster. By ditching the PSD and streamlining the design process, you aren’t just providing the client the value of saved time, you are making yourself more valuable. And ultimately, the real goal of the Post PSD Era is about creating more value — for your customers, for your team, and for you.

The graphic designer’s outcomes are just different now, even if they still use Photoshop. Instead of producing pixel-perfect mockups, their time is spent creating visual inventories, style tiles, and other artifacts that are essential in an atomic design environment.

Gideon Lewis-Kraus discusses The Fasinatng … Frustrating … Fascinating History of Autocorrect. Turns out there’s more to it than meets the eye:

A handful of factors are taken into account to weight the variables: keyboard proximity, phonetic similarity, linguistic context. But it’s essentially a big popularity contest. A Microsoft engineer showed me a slide where somebody was trying to search for the long-named Austrian action star who became governor of California. Schwarzenegger, he explained, “is about 10,000 times more popular in the world than its variants”—Shwaranegar or Scuzzynectar or what have you. Autocorrect has become an index of the most popular way to spell and order certain words.

This article also taught me that swear words are complicated. And I really like the cartoons of various autocorrect errors, especially this one:

In Doomed to Repeat It Paul Ford discusses our obsession with email and to-do list apps, and he makes an interesting point about this form of communication that we all love to hate:

Is there another form of communication besides email where the acknowledged goal is to hide all of the communication? Email has evolved into a weird medium of communication where the best thing you can do is destroy it quickly, as if every email were a rabid bat attacking your face. Yet even the tragically email-burdened still have a weird love for this particular rabid, face-attacking bat. People love to tweet about how overwhelming it all is. They write articles about email bankruptcy and proclaim their inbox zero status. Email is broken, everyone agrees, but it’s the devil we know. Besides, we’re just one app away from happiness. A tremendous amount of human energy goes into propping up the technological and cultural structure of email. It’s too big to fail.

There’s also these two little gems from the article:

Doing the work, responding to the emails—these all suck. But organizing it is sweet anticipatory pleasure.

Working is hard, but thinking about working is pretty fun. The result is the software industry.

And while we’re on the topic of email, here’s something else I’ve noticed recently:

“We’re implementing a new system to reduce our reliance on email.” “Cool, how will I know there’s an update for me?” “You’ll get an email.”

— Rian van der Merwe (@RianVDM) July 15, 2014

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.

Maiz Lulkin has a great overview of one of the most important and most misunderstood issues in software development in his post Technical debt 101:

In software development, the dreadful consequences of sacrificing quality are widely misunderstood by non technical managers. They underestimate how detrimental it is to continued productivity and morale, and ultimately, to the overall strategy of the company.

He goes on to explain why…

Ashley Feinberg in Razr Burn — My Month With 2004’s Most Exciting Phone:

It may be hard to remember now—or to believe at all, if you’re under 20—but at the time of its release the Razr was the final word in mobile technology. For the first time, you got a sleek, powerful, and wildly expensive bit of metal to call not only your cellphone but your status symbol, too. A couple of years and a few slashes into the $700 price tag later, you could barely go outside without seeing someone flip open a Razr. In four years, Motorola sold 130 million of them, a record that wouldn’t be touched until well into the iPhone’s run.

This sounds like a terribly painful experience. Like she accurately points out in the beginning: don’t try this at home…

I’m not sure if I should really link to Kids Don’t Care About Cars because there are very few things more annoying than old people pontificating about what “youngsters” like and don’t like. Still, this part did get me thinking:

The basic premise is you’ve got to go. How you get there is irrelevant. Furthermore, the costs of car ownership… the insurance and the gas, never mind the maintenance, none of them appeal to a youngster who believes all costs should be baked in.

I’m not convinced the conclusion that car ownership is a thing of the past is accurate1, even though this is not the first time the argument has been made — see Zipcar, Uber And The Beginning Of Trouble For The Auto Industry. But as an old guy myself, I do see the product opportunities that are created by this idea that how you get places is irrelevant as long as you can get there.

One of my favorite examples of companies taking advantage of this right now is car2go. It’s a network of smart cars that you can pick up anywhere, drive anywhere, and leave anywhere when you’re done. And it’s all done through a smartphone app (or the web — if you’re old and lame of course). No matter how much I think about this, I can’t get over how magical this idea is. What a great way to fill an unmet user need.

---

1. Try not having a car when you have kids… ↩

Conor Friedersdorf talks about the differences between recommendations provided by people and algorithms in Would You Rather Get Tips from an Expert or an Algorithm?

The Amazon.com algorithm is very good at using what you’ve just bought to recommend things that you’ll want to buy, [David Weinberger, a senior researcher at the Berkman Center for Internet and Society] observed, but it can be hard to tell why. Perhaps you’ll be attracted to the content of the recommendation — or perhaps it’s the fact that the cover is also green, or that the print is in Helvetica font. 

In contrast, a skilled librarian is usually going to recommend a book solely because of its intellectual value, without any lurking, contentless variables. The librarian is therefore likelier to send a person in a direction they wouldn’t otherwise have gone in a way that will advance their thinking, education, or aesthetic taste, because they’re not just meeting needs that have already been expressed.

We’re seeing this divide come out in products as well, and some are starting to use their “humanness” as a differentiator. Whereas most music recommendation systems like Pandora, Spotify, and Rdio use algorithmic approaches, Beats touts the power of human curation on their product.

Go Book Yourself is a Tumblr site that publishes curated recommendations for books you might like based on other books you read and liked. Their tag line is Book recommendations by humans, because algorithms are so 1984.

The humans are coming.

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. ↩