And the CBC shows all those kiddies what’s what.

However a secure password doesn’t need to be all of these things and password systems that require them all really annoy me.

My chosen format for passwords is the sentence. I like long sentences that won’t fall to dictionary attacks and will take forever to brute force. For instance, I might use: “Thatsjustpeanutestospace”. It’s long, easy to remember and no, it’s not my actual password for anywhere.

So it’s annoying to come up with a 33-character password just to be told:

Sadly, “password1″ passes that challenge unhindered.

And true to the Law of Unintended Consequences, the mobile site now looks infinitely better than this web site. The default WPTouch design is beautiful.

Perhaps I can just convince everyone to only look at this on their phone….

Plenty of sites get good commments, but it’s not the common case. I can’t identify any general metrics on whether you’ll have good comments, but writing opinion pieces to an audience of tech people is definitely not a recipe for civil, intelligent discussion in traditional commenting systems.

The signal/noise ratio on almost all comment systems is far, far too low to bother with in almost all cases. And personal time and energy are far, far too valuable to waste in dealing with such things.

I think we need to start measuring this one in something other than barrels. When it gets to 50 trillion barrels, its gonna be hard for the average person to digest. Lets start saying the spill has reached 7000 Walmarts of oil, people would understand that.

And then the math starts. Well played, Reddit, well played.

spec filename.rb

against a project built on Rails 3 beta and using Rspec 2 beta generated the following error (I can’t imagine why there were any issues):

/Users/chris/.rvm/gems/ruby-1.8.7-p249/gems/activesupport-3.0.0.beta3/lib/active_support/dependencies.rb:209:in `require’: no such file to load — spec/adapters/mock_frameworks/rspec (LoadError)
from /Users/chris/.rvm/gems/ruby-1.8.7-p249/gems/activesupport-3.0.0.beta3/lib/active_support/dependencies.rb:209:in `require’
from /Users/chris/.rvm/gems/ruby-1.8.7-p249/gems/activesupport-3.0.0.beta3/lib/active_support/dependencies.rb:197:in `load_dependency’
from /Users/chris/.rvm/gems/ruby-1.8.7-p249/gems/activesupport-3.0.0.beta3/lib/active_support/dependencies.rb:209:in `require’
from /Users/chris/.rvm/gems/ruby-1.8.7-p249/gems/rspec-1.3.0/lib/spec/runner/options.rb:312:in `plugin_mock_framework’
from /Users/chris/.rvm/gems/ruby-1.8.7-p249/gems/rspec-1.3.0/lib/spec/runner/options.rb:138:in `run_examples’
from /Users/chris/.rvm/gems/ruby-1.8.7-p249/gems/rspec-1.3.0/lib/spec/runner.rb:61:in `run’
from /Users/chris/.rvm/gems/ruby-1.8.7-p249/gems/rspec-1.3.0/lib/spec/runner.rb:45
from /Users/chris/.rvm/gems/ruby-1.8.7-p249/bin/spec:19

As you can see from the error it is in fact not running the rspec beta but rather trying to use the system’s rspec 1.3.0. Problematic, that.

Turns out the solution was to use bundle* to run the individual spec (this, of course, assumes you’re managing your gems with Bundler):

bundle exec rspec filename.rb

*In the project above I have a whole separate environment managed by RVM specifically for the latest über-stable Ruby (ruby 1.8.7 (2010-01-10 patchlevel 249) as of this writing), the Rails and Rspec beta.

2010-05-09 10:27:28.568 Climb_It[2330:207] *** Terminating app due to uncaught exception ‘NSInvalidArgumentException’, reason: ‘executeFetchRequest:error: A fetch request must have an entity.’

This was being thrown as a result of some initialization code in my AscentMethod class, and everything in the code looked good to me.

Turns out the issue was a naming problem. In the .xcdatamodel file I’d named the entity “ascentMethod” instead of “AscentMethod”.

Name changed, problem solved.

I feel for Jeff Atwood et al. in that, if only because I know from experience how much that sucks. When we were first launching DreamBank an issue at our host took out our entire production database as well. Heroic recovery efforts on the part of one of our developers recovered the lost data, with absolutely no help from the web host.

We promptly switched hosts because, in our instance, it was a case of professional negligence and stupidity rather than just run-of-the-mill incompetence, but that’s not the take-away from these events. That kind of thing can happen anywhere, for a thousand different reasons.

The take-away is this: we only own the data that we physically have possession of. Whether it’s back-ups of your website’s source, your database tables, or all the information you’re storing out there on “the cloud” in Google docs and Gmail, if you don’t have a current copy of it you don’t really own it. You’re just renting on someone else’s good graces.

We at DreamBank learned that the hard way. Jeff’s learning that the hard way today. Ma.gnolia learned that the hard way too (though it’s probably more accurate to say we all re-learned it). But maybe you don’t have to. Learn from our mistakes . Back up your data yourself, today.

And on that note I’m going to go back up my laptop, which hasn’t been backed up in three days, and dump the database powering this blog.

Download the script, make it executable, set it up as a shell script in GeekTool et voila. Calendar events on the desktop.

VCs are good at asking questions. They are unimplicated in your dumb decisions, unmoved by your original sense of mission and far less concerned than you that a blunder could bankrupt you. They re-imagine your business in terms of all the other businesses they’ve seen, pulling the arms off one doll and the head off another to create a perfect money-making Frankenstein. And since the stakes are high, the whole philosophical exercise tends to result in action.

Here are the questions VCs asked Redfin that changed how we think about our business.

I love question #1.