It got me thinking:

Who has done more to create jobs and improve the economy? Barack Obama or Steve Jobs.

Barack Obama has an $800,000,000,000 stimulus package to hire workers. This creates “work” but it doesn’t create “jobs.” As soon as that money disappears, so do the jobs. Should the government really be worrying about creating jobs, or should they be governing in such a way that they allow entrepreneurs to do the creating?

Steve Jobs has iTunes, Mac computers, the iPhone and the new iPad on his resumé. These products create jobs for the sellers and distributors of these electronics. As a byproduct, they’ve also created an ecosystem of job opportunities behind it. How many people have created their own jobs making iPhone apps? How many independent musicians make a comfortable living selling their songs on iTunes? How many designers are more creative and effective because of what is possible with web apps for the iPhone and iPad?

It’s not the government’s duty to “create” jobs. The taxpaying masses shouldn’t be the ones paying the bill for these few government workers. The government should get its hands out of the pie and let innovators like Steve Jobs do the job creating by making kick ass products that people actually want to buy. The government does a good job of providing a common defense and law enforcement, but it’s horribly inefficient at creating jobs.

Kid on christmas morning

I was anxious last night because I knew today could have been the day where Apple changed the ebook and publishing business forever. I looked forward to 1pm all day and the 6 hours before that couldn’t go by quick enough. I had hopes that the iPad would be some kind of e-ink, HD-color display hybrid that would make me immediately regret buying a Kindle. I’m relieved and disappointed at the same time.

Relieved that my Kindle isn’t obsolete 3 weeks after I bought it.

Disappointed that reading on an iPad will give me few benefits over reading on a laptop screen.

Kindle vs. iPad – Fight to the death only on Pay-Per-View

Elliot Jay Stocks said that ”the fact that it [the iPad] is going to kill the Kindle is now obvious.” I disagree with him. I bought the Kindle for its e-ink and open hard drive (I can put whatever I want on it). The iPad doesn’t challenge either of those so I think the Kindle will be fine. The iPad will be nothing but a bump in the road for Mr. Bezos.

The iPad will be more convenient to hold while I’m reading an ebook than my laptop because of the absence of the weird CPU/keyboard thing dangling off my laptop. The glowing backlit screen will be harsh on my eyes after 45 minutes of pure reading. I see myself reading on the iPad occasionally, but I bought the Kindle for a couple specific needs and the iPad doesn’t satisfy either of those.

I didn’t buy the Kindle to play games or check my email. That’s what my iPad will be for :-)

Sometimes my brain wanders off. I hear an interesting statement and think about that for a minute or so. I learn a lot thinking through problems on my own, but the podcast doesn’t stop when my brain stops listening.

Zone Out Button

I was delighted to find this little interface tidbit on Apple’s iPod Touch:

Tapping this button will rewind the podcast 30 seconds, the usual amount of time for one of my “zone out” sessions. This is a common activity and this button is proving useful time and time again.

Here's the affectionately named zone out button in context of the play controls.

This button made me think about what common action in my interfaces can be contained in one button. One button, one click, one tap of the finger is such a simple activity and will be infinitely usable if the user constantly does this task or set of actions.

You shouldn’t feel the need to quarantine every possible action into a single button, but think of a few task your users perform constantly and ask how you can automate that process.

Capistrano

Another example of this “single button” concept is Capistrano. It is a command line tool (meaning no visual interface at all) that allows you deploy a new version of your site to a web server by entering one command:

$ cap deploy

Without this easy-to-memorize command, I would have to manually copy the latest revision to my site from my source control repository, upload it to my server and run tests to make sure I didn’t break anything. Capistrano does all that for me. Automatically. With one command.

Capistrano and the zone out button allow me to worry less about stuff I do all the time and concentrate on the thing that actually produces value: learning from the podcast and making my sites better.

Ask yourself

• What can I do to make a few really common tasks easier on all of my users?
• How can I take some of the monotonous burden of my interface off of their shoulders and outsource a common set of actions to a single button?