Review: Belkin Conserve Surge Protector with Timer

As I've mentioned here before, I do my part to conserve energy not just to help the environment, but also to try to save a little money. Several years ago, I started turning off surge strips at night and then last year I bought some APC Power Saving SurgeArrest powerstrips that automatically turned on and off.

This, however, didn't solve my needs for my desk where I come in every morning, turn on the powerstrip work all day and then turn off the strip. While this is a simple task, when we moved, the strip that I attached under my desk was no longer a good fit, so I placed it on the floor. For the last 4 months, I've been getting on the floor and turning the strip on each morning and repeating at night, except for the nights that I forget. I had seen some of Belkin's new surge protectors and due to my laziness, I decided to pick up a Belkin Conserve Surge Protector with Timer.

The Belkin powerstrip is pretty much like every other powerstrip in that it has some outlets and a few spots for bulky power adapters. However, it had a wired button that I could put on my desk. Turning on the powerstrip became as simple as pressing the button; same goes for turning it off. If I forgot to turn it off, there was a timer that automatically turned it off after 11 hours which turns out works well for me. I turn it on in the morning and it goes off at night.

There isn't a whole lot more to say about this except that it makes shutting off vampire power supplies a bit easier than having to press the switch on the strip.

Pros

• Easy to use.
• Timer helps the forgetful.
• Has 2 outlets for always on devices.
• Has 2 outlets for bulky power adapters.

Cons

• A little pricey.
• Timer isn't configurable.

Summary

While it isn't going to pay for itself anytime soon, I'm pretty pleased with the product. It makes it so much easier for me to turn things on and when I walk away from my computer, I can easily turn things off to save even more energy. I'd love to see more people using products like these (or just shutting off powers trips when not using them) as we could cut a lot of energy usage that is simply wasted.

Making a first impression

When applying for a job, the standard thing to do is to submit a resumé and that becomes the first impression that a potential employer has of a candidate. Many years ago I came up with a basic, clean format for my resumé and periodically have updated it (luckily not lately), just in case I needed it. While I'm not sure a resumé ever helped me get a job (I was referred by a friend to the one job that I landed where I submitted a resumé), I've been in the position that I've had to read resumés of potential candidates. I look for a number of things on resumés to see if the candidate is worth pursuing. These include the basics like:

• Does each job tell me what the candidate did?
• How much experience does the candidate have in a particular field? Lately, it has been iOS and Objective-C.
• Has the candidate worked on a team? What was the candidate's role on the team?
• Has the candidate switched jobs a lot?

And the not so basics:

• Is the resumé clean and professional looking? I like to see PDF resumés as I don't use Word and formatting gets messed up with Pages.
• Are there spelling errors?
• Is proper grammar used? While no one is perfect, I know that I spend a lot of time on the 1-2 pages of a resumé; I expect others to do the same if if grammar isn't a strong trait, then the candidate should ask for help in reviewing it.

Some people will say that I'm too nitpicky, but I'm in a field where attention to detail really matters. I recently saw "Got familiar with xxx" as a bullet item on a resumé. That strikes me as someone that didn't spend enough time wordsmithing or didn't have a good grasp of the language.

There are also some things you should leave off a resumé. In the current era where everyone has an app or two, I see people list how many apps they have. One went as far as to say he worked on 50 apps. Going back to my list above, I looked for how long this person worked at a company and then did a rough calculation that he put out 1 app every 9 days of employment. While the candidate might have thought that the quantity of apps was important, it turns out to be a negative in my book as 9 days isn't enough time to write a quality app (granted some apps were probably cookie cutter and different content put in).

I remember in the past my father making sure he put his resumé on the right paper stock just to make a good impression. He put so much effort into his resumé that when it came time for me to do a resumé, I tried my hardest to make it my best work. In modern days, people rarely send in paper resumés, so they have to do different things to make a good first impression. I wish more people would spend time polishing their first impressions.

Jumping on the upgrade treadmill

Now that Apple has announced the iPhone 5, it's time for me to upgrade! Yes, I did just get an iPhone 4S last year, but luckily for me, staying on top of iPhone technology is part of my job. Now that my wife has an iPhone, it's easier for me to justify upgrading as I can give her my old one and get the discounted pricing. Would I pay full price for one? That's a tough question that luckily I don't have to answer.

I don't think I've been so enamored with devices as I have been with the iPhone. Initially I was pretty ho-hum about it because I felt I had to be against it due to all my work centering around competing devices. While the improvements of each iPhone seem pretty minor, I can imagine them being quite useful to me. It isn't cheap to keep upgrading devices, but as my wife puts it, I deserve it as I work hard.

Will I be first in line to get one? I won't go out of my way to get one, but I'll order when I can.

Bulk updating of git repositories

As I've written in the past, I have mixed feelings about open source, so I take a close look at a lot of it, especially for some side projects that I have. There is a lot of decent code out there, or at least ideas that I can build on, so I've flagged code to look at and cloned a bunch of repositories from Github. The problem I've been faced with is that I have a folder filled with open source that becomes out of update quickly and updating each repository is cumbersome. I want to have the latest and greatest so I don't have to think twice about the code when I go to evaluate it or use it.

Today I had a little time, so I threw together a shell script that walks through my open source directory and updates each repository in it. I could probably set this up us a cronjob, but for now, I'll run it manually. For all those out there that want to do something similar, here is the script in all its glory!

#!/bin/sh
OIFS="$IFS"
IFS=$'\n' 
for i in $(find "/Users/scott/Documents/Development/OpenSource" -type d -maxdepth 1); do
    cd "$i"
    echo "Pulling from: $i"
    git pull
done
IFS="$OIFS"