6 second rule

I have this rule for trying out new software: if any single step of installation or configuration takes longer than about 6 seconds, I will probably delete it: all it’s data, it’s registry entries, environment variables, everything. If it’s that hard to install and configure, it’s probably going to be difficult to use as well.
This is nothing personal against the developers of any software.

Over the years, I have packaged and distributed code using hand-rolled tar.gz files, .zip files, NSIS executables and the GNU auto* toolchain. I am sure some of my code violates the 6 second rule as well. I don’t take it personally if someone returns the favor above.

My time is really valuable to me. Time spent investigating new software is time I could be billing, or time I could be surfing, or shooting pool, or time I could be spending with my girlfriend.

Through a series of posts on this blog, I will detail various violations of the “6 second rule.” With each post, I will also try to find and post a (working) solution to the problem.

List of recent 6 second rule offenders

Note: It’s likely that the time I spend writing up these 6 second violations I could have found a work-around. But that’s not helping anyone do a better job. Actually, what other people do is becoming increasingly irrelevant. I can use the violations as a way to do a better job myself. So it’s worth it to me to keep a record.

• [09/13/2009] Slideshare.com user profile page. I filled out all the required information (a lot in my opinion) and browsed for my standard photo to upload. Turns out the photo was too large, and when the profile page reloaded, none of my information was saved. Most annoying as I checked for profile photo shape and size restrictions beforehand, and I use that profile photo on a lot of other sites.
• [06/21/2009] Disqus commenting system, totally unintuitive for me with respect to their “blogging system.” Just didn’t get it and when I tried to delete it, even more confusion.

  Verdict: partial fail. Customer service was responsive and I have no problem with Disqus commenting.

  This should be easily fixed with very clear documentation, and possibly rethinking how they are defining words like “blog.”

• [02/19/2009] Yahoo developer ID. Followed the instructions, failed to verify my web site. Given that I have performed similar html file verification for google on 24 web sites, and this failed on my first attempt, I’m not impressed.

  Verdict: FAIL.

  Yahoo needs better documentation, and better process for acquiring developer IDs. If Google can make it simple, stupid and colossally useful, Yahoo should do it as well.