Ramble On

So I can’t type all that fast and I already knew the wife could type much faster than me - but… well, you have to read the transcript.

me: http://labs.jphantom.com/wpm/
brown-eyed girl: 71 wpm, 91 wpm, 92 wpm
me: well
me: I was 67 wpm with 8 mistakes when I tried it
brown-eyed girl: well
brown-eyed girl: I kicked your ass!
brown-eyed girl: 94 wpm, w/ 6 mistakes
me: I think I might have to blog the “I kicked your ass!”
brown-eyed girl: OOOO
brown-eyed girl: 115!!!
brown-eyed girl: and NO mistakes!
me: show off
brown-eyed girl:
brown-eyed girl: damn straight!
brown-eyed girl: I can’t believe I bested the boy in something computer-related!!!
brown-eyed girl: wow!!!
me: never take on a copy editor and english major in a typing contest

Time to take high-school typing again. “Now is the time…”

From Terry Chay:

At work one of the printers is named “paperjam” and the other is “treekiller.”

I printed out my stuff on treekiller.

I so now want to ask NC Extension to name our group printer “PC Load Letter”

Damn, it feels good to be a gangsta.

So I’ve written about this before - and it turns out that a lot of the “require_gem” deprecation warnings come from tasks in your gem builds that build convenience scripts in /usr/bin (or wherever on your system it places these). So if these convenience scripts (like /usr/bin/mongrel_rails) are left around from installs with previous versions of rubygems - just reinstall the gem (or change all the require_gem statements to just “gem“) yourself.

A grep require_gem /usr/bin/* is pretty convenient to get an idea for the gems you need to reinstall.

However, feedtools 0.2.26 has a bunch of require_gem statements in lib/feed_tools.rb (and littering my crons with the deprecation warnings), so I ended up building and distributing my own replacement with require_gem replaced with gem.