Archive for the 'Technology' Category

Monday, May 3, 2010

Let’s try not to be too glib

From How Wired.com Tracked the iPhone Finder:

In response to Wired.com’s scoop identifying the finder of the lost iPhone prototype, many have asked me how we did it. The process of uncovering digital footprints to identify Brian Hogan was indeed challenging and enlightening, so I thought I’d tell the story here. Heck, it might even teach police officers a thing or two so they don’t have to kick down doors.

Wired certainly deserves some credit for breaking the story. Initiative in this day and age of blogs usually get you the good kind of attention. However, it doesn’t give you free license to be a jackass and make smarmy comments that make no sense.

The facts are that:

  1. The police were able to search Jason Chen’s home because what they did can be considered illegal unto itself.
  2. There is no data to suggest that the police seized his drives to find the iPhone finder.
  3. Breaking the door down is completely justified because no one answered the door. Why? Because otherwise every two-bit cyber thug would simply ignore the police knocking on the door, delete all their data, and then let in the police. At which point, the police would be criticized and called inept for not breaking down the door. You’re naive if you believe otherwise.

Wired, kudos on your exclusive and please tone back the glib.

Wednesday, April 28, 2010

Saying it without really saying it

If you were confused about whether Apple was still committed to the Mac, their lack of Apple Design Awards for anything Mac pretty much says it all.

The Apple Design Awards 2010 recognize iPhone OS applications that demonstrate technical excellence, innovation, technology adoption, and quality.

Wednesday, April 21, 2010

Quick iPhone time-saving tip: App Store

Put you App Store icon on a less frequented page. You’ll feel less compelled to check for updates and look for new apps.

Friday, April 2, 2010

Fighting Stupidity with Stupidity

Cory Doctorow wrote a piece on why he won’t be buying an iPad (which extends to why you shouldn’t either. I don’t agree with his article, but the vehement arguments against some of his have been equally asinine.

Joel Johnson wrote an otherwise brilliant piece that says:

So what if you can’t make iPad programs on an iPad. I don’t complain I can’t make new dishwashers with my dishwasher.

Doctorow doesn’t outright call this out as an issue, but it fits with the theme of what he wrote. The problem is this is analogy is flawed. Let’s see if you can tell the problem with it if I put it in mathematical format.

iPad programs : iPad :: dishwasher : dishwasher

It becomes rather clear, doesn’t it? It’s essentially saying that iPad programs are iPads unto themselves. Let’s make it even worse.

Apologies to Dan Jalkut (I love MarsEdit; don’t hate me), but this gem is even worse.

“You can’t write apps for the device.” Yeah, and you can’t publish a book with a book. Or write a pen with a pen.

Joel’s analogy almost worked because he started talking about appliances. It goes wrong from there, but the groundwork is there. The above is just wrong from the get-go.

This isn’t to say I agree with the concept. Is it important to be able to develop iPad applications using an iPad? No. The ability to create content for a platform using the platform itself isn’t important. It’s really not. Computers are one of the few (if only?) devices that do this extensively. Let’s use some other (slightly more valid) analogies to argue against this idea.

You can’t make PS3 games using a PS3. You can’t make movies using a Bluray player. It’s easy. I’m sure you can come up with some as well.

The fact is that for consumer devices (which the iPad is), it’s not important to be able to develop content for it with the device itself. I agree with you. But I’m also begging you all to stop using bad analogies to argue this truth.

Wednesday, March 24, 2010

My horribly incomplete backup plan

It’s been a long time since I took a hard look at my backup situation, but a series of blog posts in my reader has caused some naval gazing.

A long time ago in a computer far far away

My backup plan was once dead simple. I used CCC or Super Duper to create a clone of my boot drive whenever I thought of it. Sometimes I was good and did it weekly, sometimes I went months without.

Thankfully I had no crashes during this period. I never had to experience the frustration of losing a month of data.

Let’s do the time warp again

Time Machine! I was so excited when I finally got a drive to use with it. I turned it on and got frustrated any time it monopolized my I/O attempting to back up. Honestly I can’t tell you if specifically Snow Leopard fixed it, but I haven’t gone searching for the Time Machine menu to stop the backup for a long time.

I still did my Super Duper backups, but it became less of a priority because it wasn’t automated.

Disaster

It finally happened. I lost my boot drive (which was under warranty thankfully). I could cool off the drive and get a few minutes of work, but not enough time to do a Super Duper backup and I/O just made it die faster. I was using my Super Duper drive to temporarily back someone else up.

Luckily, I had a Time Machine backup ready to go. That was almost not the case as just weeks before I finally replaced the power supply on my Time Machine disk (thank you OWC for quick diagnosis and replacement).

It was time to see if the machine would do its job.

It just worked

Once I got my replacement boot drive, it was time to stick in the SL disk and try the restore. As you can already guess, it worked. I selected my Time Machine disk and initiated the restore.

Your mileage may vary, but Time Machine is now my preferred method for incremental and bulk backup. There are a few reasons why.

  1. I don’t have to do anything to keep it up to date. Seriously, no matter how many calendar reminders or OCD you are, backup plans fail when you need to do something on a schedule rather than the machine do it for you.
  2. It protects you from your own stupidity. Clones are great, but they won’t help you dig out a file you deleted three weeks ago unless you either didn’t backup since then (shame on you) or you keep a clone rotation large enough to have a backup old enough (expensive and impractical for most as well as having the problem of requiring lots or manual interaction).
  3. You can do a bulk restore easily despite it not being a bootable disk. Stick in your Mac OS X install DVD and you can do it with a few clicks.

The moving target

Time Machine works great if you have a desktop or regularly connect your computer to a series of peripherals, but I haven’t chained a laptop down like that in years. Needless to say, the cloning plan I used on my MacBook wasn’t working for me.

I could in theory use a Time Capsule to use Time Machine for this situation. Problem 1 is that I’m cheap. Time Capsules are expensive. Problem 2 is that assuming I could get it accessible using Back to My Mac behind my FiOS router, it’s not really supported.

The solution was to use Crashplan. If you use their software to backup to another computer belonging to you or a friend, it’s free. I have a computer that’s on a lot with lots of storage and it’s own backup plan in place! I installed the software, told the Mac Pro to use a specific hard drive as the destination, and initiated backup from the MacBook.

Now anytime the two are on at the same time, the MacBook will back up to my Mac Pro regardless of local network or over the Internet proximity. Crashplan has fantastic in the background incremental backup. It meets the requirement of doing its work without me.

I only have it set up to back up my home directory, but I don’t store significant irreplaceable data anywhere else, so at worst I reinstall and then restore my home directory.

The Achilles heel

As written (correctly) elsewhere, my backup plan is incomplete. One fire at my house would wipe it all out. More specifically, my plan doesn’t include offsite backup.

When I finally stop being cheap (can’t help it), I will probably sign up for Crashplan’s subscription service. I have two options for that.

  1. I purchase the single computer plan and backup only the Mac Pro. That actually covers both computers.
  2. I buy the family plan and set both computers to use it. The MacBook would still back up to the Mac Pro as well because assuming I connect it to my network, restoration would be much faster from the Mac Pro. It also lets anyone living with me back up their computers.

I’m not saying my plan is a blue print for everyone else. I am saying that you need to consider the profound importance of a backup strategy that requires no action on your part. The biggest risk in any backup plan is always you. Backups are for the improbable situation. The most probable unfortunate event is you failing to connect your backup drive and running your backup software. Take it out of the loop, or at the very least, make it a redundant bonus.