We’re all creating a lot of content these days. We write blog posts, share our location, store links, microblog on Twitter, and more. Others can see the latest stuff, subscribe to updates in RSS, and view individual chunks of content.

In many cases, seeing old content in context is difficult. I can look at one blog post from a year ago. I can’t get from there to the posts the author wrote immediately prior or after. Most blogs are set up with an expectation that the most recent content is the most important.

New stuff matters most, but old stuff also matters.

The problem of context becomes larger with microblogging. The timeline shrinks. “Old” becomes hours, or even minutes. Understanding a single tweet sometimes requires the context of knowing what was said in the previous tweets.

For example, say you stumbled into this message:

What is Chris talking about? Wouldn’t it help if you were able to see his previous message, which mentioned he wasn’t going to wear trousers all summer?

Flickr does this well. Every photo is shown within the context of when it was uploaded:

We see an after picture. What’s it take to see the before? A single click on the thumbnail. And if we need more context, we can click browse and be taken directly into that photo’s spot in the stream.

I understand that providing context is a secondary job for lifestreaming services, which are so focused on what’s happening right now. But as long as the content is available, it will be indexed and users will become confused if they can’t figure out where they’ve landed.

How can you provide some context on some of your site’s more buried pages?

Photo credit: Bill Jackson III

If you’re lucky enough to have a Chipotle near you, chances are you already appreciate the simplicity of their menu. There are only a few ingredients, so there are only a few options (okay, well technically there are over 60,000 different combinations, according to Chipotle ). Taco Bell, on the other hand, keeps inventing new words to describe the same few ingredients.

Dustin Curtis notices the same thing about the In-N-Out Menu.

(Yes, this is from my 2007 Ignite Portland talk, but it never made it into a post until Mike Duffy pointed me to Dustin’s)

When I spoke at the first Ignite Portland, I said simplicity is two-fold. It’s about making things easier on your users, but it’s also about making things easier on yourself. When you’re lucky, you get to do both at the same time.

That’s the case for Ken Anderson and Janice Flint, husband and wife owners of Crystal Springs Software. Ken left his job at Adobe after 21 years to found the company, which makes iPhone apps. Its first product is an addictive little game called iZilch.

I’m sure Ken and Janice have many great iPhone app ideas, but they started with a simple dice game. The rules are straight-forward, so there weren’t a whole bunch of features to add before they were able to launch. They focused instead on finding the core. Although, Ken says it’s not quite as easy as it looks:

“Since it is a dice game, we focused the user experience on the dice and how you interact with them.  You drag the dice with your fingers to score.  You roll them by shaking the iPhone… All this results in a very transparent user experience, a game that sweeps you up and moves you along… It is actually a lot more work to design software this way, though the scope of this project is still small.”

Ken and Janice chose to focus on creating a few polished features instead of a whole bunch of fluff that doesn’t flow. Even better, they were able to get their first app out in just a few months. That’s counting the time it took Janice to learn the platform.

All the while they were creating the simple life they wanted while raising their four teenage daughters. Their primary goal was not to cash in on the riches of the iPhone platform. The objective was a lifestyle change. Ken says he misses some parts about working for Adobe, like having hundreds of people focused on the same goal. But, they’re enjoying their work, even if it is a little different:

“As an Indie developer, you have to do everything yourself, and you can’t do all of the traditional things that a big company does to make a product successful because you don’t have the resources.  Hopefully, we will be able to hang in there, build great products, figure out how to let people know about them and grow a sustainable business on our own terms, but it will take some time, and like iZilch, some luck.”

My friends at Wired are on their side. Chris Anderson wrote a cover story this month about The New New Economy, where there are more companies, each with fewer people. An old BestPlaces joke was that we only had a handful of people because in big companies, there are only a few people who really work.

In Crystal Springs Software we see two people choosing a simpler life and creating simple software. If this is the future, we’re doing pretty good.

It’s easy for technologists to get lost in the technology. We’re around it so much, we start thinking like technicians.

Sitting at my favorite tea house the other day, I was picking Andy‘s brain about memcached, a back-end technology that’s really beyond the type of web work I usually do.

It turns out that what I thought was complicated is really rather simple. At least, it seemed that way after I read the caching story:

“Two plucky adventurers, Programmer and Sysadmin, set out on a journey. Together they make websites. Websites with webservers and databases. Users from all over the Internet talk to the webservers and ask them to make pages for them. The webservers ask the databases for junk they need to make the pages. Programmer codes, Sysadmin adds webservers and database servers.”

No, this isn’t a story that makes memcached accessible to the complete newbie. For a programmer who normally stays away from sysadmin tasks, likely a common memcached user, it’s spot-on. The story gives a perfect use case, adds personality and takes me quickly from knowing next-to-nothing to almost being able to implement it myself.

Other Open Source projects could stand to learn from this. Heck, so could any technology that requires documentation. This stuff isn’t just for marketers.

What do you wish came with its own story?

If you don’t read frequently updated websites using a feed reader, you really should. I assume most of you are probably reading this outside of adamduvander.com, but if not, go learn how to get automatic updates from a feed without having to visit the site. Nothing will simplify your online life more.

I’ve used a number of feed readers over the last five years, starting with Bloglines and moving on to NewsGator recently giving in to Google Reader. I don’t think any of them have the perfect interface. Until today, I didn’t think I could describe what that would be.

A feed reader should look like email. At least, I wish I could use my feed reader in the same way I use email. I keep my inbox clean, I filter out the stuff I don’t ever want to see (spam) and I save non-urgent messages for later.

In a feed reader, I want to be able to glance at the latest content and tell the reader one of the following:

• Delete it
• Read now
• Read later
• Never read anything like this

Many readers are able to get close to this, but they have a problem with the last one. Too much noise in the signal can keep a lot of us from adding more feeds. There needs to be a simple way to mark the type of content you don’t want.

As an example, there is a blog I read that has great content, but also has a daily feature that I never enjoy. I would love to get the feed from that blog without that daily feature. I’m a geek, so I could create a Yahoo! Pipe to do what I want, but I shouldn’t have to.

The filtering technology should be within the reader. Wherever possible, it should be automatic, the same way my email program learns what I consider spam.

For many people, the email analogy will fall flat. Your email might be overflowing. You might be overwhelmed at the thought of another inbox. In that case, you appreciate the problem of information overload. The answer shouldn’t be less information overall, but instead smart processing so that we only see the part that matters.