AB Testing for time on page with Optimizely

Sometimes, like say if you go with a longform landing page, a metric of success is going to be just how many folks stuck around long enough to read. After all, if you put your call-to-action in the footer, there's no sense optimizing it if 90% of your visitors aren't…

Where to find Ruby developers to hire, online and off

I'm taking a break from trying to create books and products and things. Those efforts weren't going all that well, but the content I produced for it I'm particularly proud of. The section below is a slightly modified chunk of what was to be "The Technical Recruiter's Guide to Ruby…

The Try-it-on Approach

When lunch is impractical (as with remote candidates), you have to find another way to backstop your research findings and figure out if this developer is any damn good. You can do a lot of this over the phone, mind you, but it’s never going to be the same…

Why are you hiring?

You need to know why this developer decided that weed-infested, brown grass of his new employer is greener than yours. Image by Robert S. Donovan, used under Creative Commons This is the first question you need to ask, because it informs most everything else. Essentially, the environment you're hiring into…

Your hiring mindset

The reasons for why you're hiring have a great deal of impact on how you go about the hiring process. If you're hiring because of another developer leaving, you're going to be much more time-crunched than, say, a situation where you need more developer bandwidth for upcoming projects or simply…

Developer Stereotypes: The Neckbeard

The next in a series of posts walking through various developer stereotypes. Read the first entry to get a better idea of what this is all about. Know Your Neckbeard If you've worked in or with a traditional IT department, you'll know this type right away. They're the by-the-book, dogmatic…