I was reading Robert Scoble’s post on social networking resumes the other day. While I haven’t been laid off, I think his post is relevant to everyone. But it got me thinking. He makes the the suggestion that
Your blog is your resume. You need one and it needs to have 100 posts on it about what you want to be known for.
photo credit: adria.richards
That’s good advise, but I don’t do a very good job of that. My professional time is spent between UNIX infrastructure work and web design and development. Yet about 1% of the content on this site is relevant to those disciplines. Lately it seems like most of my writing here is about the iPhone which is 0% of my professional time.
I have been thinking about why that’s the case. Most of the UNIX infrastructure work I do is fairly proprietary and not appropriate to write about publicly. It’s not simply a matter of keeping company information private. It’s also that a lot of what I deal with on a day to day basis just isn’t interesting or applicable to anyone who doesn’t work in the specific environment where I work.
On the web design front, we have a blog at Communications Tool & Die but I have such a limited time to write that when I do have time I tend to post here instead of there. The other side of that coin is that Communications Tool & Die doesn’t have all that much work and unfortunately there isn’t too much exciting news to write of there.
The upshot is that while I actually am a very senior UNIX infrastructure person, it’s really not at all clear from what I write here. I think I can change that. I’m not exactly sure how, as I don’t expect to start writing about my day job all that much. But I can start to include more infrastructure relevant content. What that content will be is not immediately clear to me, but I’m going to give it some thought and hopefully change the tone here a little bit.
Of course, I’ll probably still keep writing about my iPhone experience because I love my iPhone.