The EU forgets

In 2007, I criticized what I considered to be an unworkable plan to institute forgetting on the Internet. The idea was to mandate that providers delete one's records after a certain time. That way, for instance, your teenage antics wouldn't follow you around forever and you can rest assured that your duckface pics and embarrassing status messages would expire.

According to Jeffrey Rosen, the EU has now proposed internet forgetting as a universal right - and not in the context of expiration, but rather in the context of individual requests:

The proposed right would require companies like Facebook and Google to remove information that people post about themselves and later regret—even if that information has already been widely distributed. 

So if your 2007 duckface pic embarrasses you in 2012, you can delete it from Facebook. If your friends shared it, you can ask Facebook to delete it from their streams too. A journalistic exemption exists, presuming you can make a case for it - if you can't, and you remove it anyway, you face a million-Euro fine. And

Moreover, the right to be forgotten can be asserted not only against the publisher of content (such as Facebook or a newspaper) but against search engines like Google and Yahoo that link to the content. 

So if you're Rick Santorum, you can tell the search engines to remove content.

As Rosen argues, this EU law conflicts with US First Amendment rights. The impact on US companies doing business in the EU - such as Google - remains unclear.

Hints in Skyward Sword

PopWatch has an interview with Shigeru Miyamoto, the director of the Legend of Zelda franchise (among others), about his choices in designing various games. Since I just finished the most recent Zelda game, Skyward Sword, I was interested in what he had to say about the hint system:

In Skyward Sword, there’s a magic stone that will give the player hints if he gets lost. It reminds me of the Super Guide/Cosmic Guide function in New Super Mario Bros. Wii andMario Galaxy 2. Now, when I was a kid, I spent days trying to beat some of the difficult levels in Super Mario Bros. 3. If you could go back in time, would you create similar guide functions in those games? 

Back in those days, the ways in which we could entertain people in the videogame world were rather limited. And because of that, [having the gamers] find out any and all the solutions themselves was one of the most important elements. Today, there are many, many ways to entertain people in one single videogame. And the Internet has made it so easy for people to ask for clues. We are mindful of that changing circumstance. Whenever we are making the game, we are making it for those who really need and want to know about a solution or a hint. But there are those who do not want to ask for those kind of hints. They really want to solve any riddles or challenges for himself, for herself. We are mindful of both of these types of people whenever we are making these games today.

Fascinating! Anyone who's played a Zelda game can tell you how tempting it is to peek at the many walkthroughs and FAQs when they're really stuck on a puzzle. Miyamoto can't wipe out those external guides, but he can create a sort of safety valve that gamers can use - or ignore - and that may be easier to use than taking the time to google a FAQ. Great example of how to set up a system that gives people choices within a coherent framework.

Don't just send in a resume: How to write a letter of application

Over the years, I've given a lot of people advice about how to write a letter of application for a job. Many of them have taken my advice - and they usually get the job.

What's the advice? It's all about what the letter is supposed to do.

What's the letter of application?
People often think of the letter of application (or "cover letter") as, at most, a way to specify what job they want and how much they want it. The heavy lifting, they figure, is done by the resume. In fact, many people don't even write a letter of app, they just send in the resume.

In most cases, this is a terrible idea.

It's a terrible idea because the letter of application really performs a very specific, important function. Think about it this way:

Your skills and abilities

Their needs

You have skills and abilities. They have needs.

These are represented in certain genres:

Your skills and abilities		Their needs
Resume		Job description/ad

Notice that a vast gulf separates the two. The resume serves as a sort of fact sheet about your skills and abilities, education, experiences, and so forth - all the things that you might bring to bear on a job. The job description represents the employer's needs. At this point, you may look at a job description and say, "hey, my skills and abilities fit their needs." But they may not be able to draw the same conclusions, and even if they do, they may not see the match as clearly as they will with other resumes.

That's especially true when your skills and abilities must be inferred from one context to another. Here's an obvious example. Suppose that they need someone who has experience leading a team in solving work problems. You're about to graduate from college, so your jobs have not been leadership jobs - you've served as an intern, as a junior analyst, etc., but you haven't led. You have, however, led in other contexts: you've held officer positions in your sorority, in your synagogue's outreach program, etc. And some of those leadership experiences look a lot like the one described in the job ad - more than might be casually obvious.


So you need something to fill the gap. I bet you can guess what it is.

Your skills and abilities	How your skills and abilities meet their needs	Their needs
Resume	<- Letter of application ->	Job description/ad

The letter of application, done well, interprets the resume for them in terms of the needs they outlined in the job description. In a sentence, its message is: "You need X, and I can provide it."

How do I identify and rank the needs?
First, you'll identify the needs listed in the job ad. For this, print out the ad and use a highlighter to highlight specifics in the ad (these may be listed as skills, duties, or requirements). Often you'll generate a long list.

Next, make sure that you can make a plausible case for filling these. If you can't - for instance, if they ask for four years' work experience and you don't have it - don't waste their time and yours. If you can, proceed.

Next, rank these needs. Some will be pro forma (ex: "four-year college degree required"). Others will be very specific to the job, and these will probably be ranked more highly. If you can leverage them by linking multiple needs together, you're ahead of the game.

How do I write the letter of application?
First, outline your letter of application. I recommend using the same approach that I use when writing letters of recommendation: the much-reviled five-paragraph essay.

Why? For this task, the five-paragraph essay is perfect. You need to write a letter that:

• identifies a focused set of needs and your ability to fulfill them;
• succinctly signals its structure for the harried HR folks who are having to read hundreds of these letters; and
• ends with a clear next step for them.

So I recommend the classic five-paragraph essay structure. It'll look like this:

1. First paragraph: Introduction. I want this job, and I'm qualified because of A, B, and C. These match your needs.
2. Second paragraph: I have the qualification A. Here's some examples from my resume (and maybe elaborations or other stories).
3. Third paragraph: I have the qualification B. Here's some examples from my resume  (and maybe elaborations or other stories).
4. Fourth paragraph: I have the qualification C. Here's some examples from my resume (and maybe elaborations or other stories).
5. Fifth paragraph. So I have qualifications A, B, C. Call me.

This approach is by-the-numbers, but it's also very clear and on-message. Notice that if you have four points instead of three (A, B, C, and D), you'll simply add another middle paragraph to generate a six-paragraph letter. 

Next, you'll flesh in the sections. What you'll generate may look something like this letter. It's straightforward and functional. It's simple, but it packs in a lot of information and relates it directly to the applicant's resume, interpreting it in terms of the specific job. And its strong framing at beginning and end help the reader to understand exactly what's covered. 

Will this letter of application get you the job? I can't say. But I can say that if you follow these steps, you'll at least generate a solid link between their needs and your skills. Good luck!