I'm a Ninja and I'm OK

I tend to peruse the job openings posted to LinkedIn and other such sites. There is some value in keeping up with who is doing what by watching hiring needs (don't worry, GoDaddy, I'm not on the market). Something I've noticed lately, though, is that a lot of companies are starting to add statements like this to their listings:

"Anyone with 'Ninja' in their title need not apply."

Now I get the sentiment - companies aren't interested in people with inflated egos or a disproportionate assessment of their abilities and worth. But that said, lighten up, Francis.

If you check my LinkedIn profile, you'll see that I list "Powerful Internet Ninja" as my title when I worked at Demand Media. As I said in my profile, there are those who look down at using "Ninja" in a job title. To those people, I say lighten up. I did some pretty cool things at Demand Media, many of which were, while completely moral and ethical, somewhat sneaky in terms of strategy and competition. "Ninja" describes what I did sometimes, and it just sounds cool. If you think that detracts from my skills or makes me somehow pretentious, I will politely smile and disagree.

In other words, it's pretty clear I don't take titles seriously. Anyone who is disqualified from consideration based on the fact that they get a little humor out of their self-claimed title (along with, let's be honest, self-claimed experience) probably doesn't want to work at such a company, anyway. That's a pity, because some of the best technologists I know have senses of humor that make mine look absolutely pedestrian.

Then again, maybe such a line in the sand is a good gating function for everyone.

Tags:

Linkbait Comes to Television

I spent the evening last night at an Irish Pub (yes, I know, this blog entry can just stop here) watching the Seahawks game. Remember, though I live in Silicon Valley, I'm a Seattle transplant. Go Hawks.

As I and the 50+ fans were enjoying a convincing victory, a commercial came on. It was entitled (and captioned), "The Call," and depicted a woman getting a phone call. She says hello, and her face drops as she listens, clearly being shocked at what she is hearing. I, the viewer, know only her shock - there is no indication of what's actually said.

And then the commercial ends with the call to action to go to a URL to find out what happens next.

No. Just no. Clickbait online is one thing. Doing it in a broadcast television commercial? Sorry, that's farther past a line that's already been crossed.

I encourage everyone to refuse to go to any URL presented in this manner. Please help send a message to advertisers that this simply won't work.

Oh, and get off my lawn.

Tags:

A Designer's Guide to DPI

My friends over at Media Temple have promoted a fantastic guide to DPI, and so much more. This article really covers it all and in an outstanding way. I can't recommend it enough. Thanks to Media Temple for pointing it out, and thanks to Sebastien for writing this. Bravo!

http://sebastien-gabriel.com/designers-guide-to-dpi

Facebook to give away how magic tricks are done

Well, not really, but just as stupid. As reported by Ars Technica, Facebook is now placing a [SATIRE] tag next to links that go off to The Onion. Clearly, Facebook is ruining the fun for those of us with enough brain cells to recognize satire when we see it, and is making the presumption that most of you are idiots.

Rumor has it that next week they'll be threatening to disclose the true identity of Santa Claus to anyone under 13 who lied about their age to get an account.

Hey Facebook? You want to do a little editorializing? How about you flag all of those linkbait sites as [DOG CRAP] while you're at it? Now that would be a non-abusive use of your power.

Revisit and Refactor

Today I revisited some code I'd written about a month ago and reduced the time it takes to run a data loading job from 52 minutes down to sub-10 minutes by replacing a relatively slow API call with a direct call to local code. This is something that was "good enough" until now, but was on my radar as being eligible for improvement. Since I had a new data loading job that would take over 10 hours using the API call, I had to write the new job a better way. Copying this better code back where it could make a difference meant that all of my data loading jobs were now refactored and much faster.

The takeaway here for developers is to periodically revisit your code and refactor it. Find new efficiencies. Examine how your code has been working and consider what you might have learned since the last time you worked on it. You may notice something now that you didn't notice the last time you were in the code.

A small amount of time doing this can pay off in huge improvements.