I feel incredibly sheepish looking back over a week and not seeing that I’ve learned that much. Either I really haven’t, or I’ve neglected to write it down, either way I’m not pleased with myself.

Those who follow me on Twitter may have already seen this photo, but I wanted to share the story behind it.

An interesting part of the hiring process at Lookout is the candidate presentation. The presentation is meant to introduce the individual to the entire company while giving them an opportunity to wax poetic on a topic the person is passionate about.

This past week, despite moving apartments across Berkeley on Wednesday, I managed to learn some interesting things here and there.

I went to the impromptu redis SF meetup yesterday at Epicenter Cafe in SoMA and I figured I’d write up some notes about it after the fact.

Unfortunately I didn’t seem to learn that much this past week.

Following last week’s learnings, here’s another dose of little bits and pieces I’ve learned over the past week or so.

It is a little (unknown) fact that my first job as a software developer was writing C code, for the network group at Texas A&M University. Like most student developers, my work never saw the light of day, mostly because I never finished it, but I did learn an incredible amount working on my little project made for one.

I recently discovered that the branch manager at the Wells Fargo bank I frequent can order a bound stack of two dollar bills on request. This is rather handy since banks don’t normally have any just “lying around.”

About a month ago I changed jobs, leaving Apture to join a start-up in a completely different space: Lookout, Inc.. While I won’t delve too deeply into my reasons for leaving, my reasons for joining were almost entirely driven by the team. I was fortunate enough to meet with Kevin and John (CTO and CEO respectively) through a mutual friend and some time after that Dave G., the tech lead for the server team. The more people I met from Lookout, the more I wanted to work there.