So, of course, I started with my usual process of thinking (and thinking some more) before actually doing anything. What is a bio, really? What do I want to say? And what is the client looking for? My basic conclusion – the client wants to see value for their money. So a good bio needs to show that I know my shit, that I’ve been around the block, and that I make a good teammate. I also decided to add a sugary coating with a little humor.

Here’s what I came up with:

Justin has five years of experience in end-to-end software development, and spent the last two building large scale, consumer-facing web applications with Adobe Flex. He brings a unique combination of “what’s cool” frontend design experience with secure and efficient enterprise-class backend architecture. Justin is also a passionate leader and coach, familiar with development teams and the development process.

In his younger years, Justin earned his PhD in physics before turning to software engineering. His Evil thesis advisor had him working day and night on a portable laser beam system that could be mounted on the head of a shark.

When I re-read it now, it certainly comes off a little used-car-salesman-ish. But it’s all true, except for the sharks. (I actually did quite a bit of laser physics for my thesis, so it’s not complete bullshit.) I also like the tone – it reads knowledgeable with a touch of Austin Powers dashing. I found it interesting during the writing process that with too many resume-type details my bio sounded phony, like I was trying too hard to impress. As I began to prune them away, I was able to achieve the knowledgeable tone I was hoping for.

The primary goal for this blog is my writing. I desperately want to be a better, faster writer.

Once the choice of a primary goal is made it acts like The Force–and as Obi-Wan says “The Force is what gives a Jedi his power. It’s an energy field created by all living things. It surrounds us, and penetrates us. It binds the galaxy together.”  Everything in this blog, especially code-filled posts about Flex animation or Nginx configuration files, will always be about my writing (that’s the surround and penetrate part that binds this blog together).  I want to find a voice that is terse, but informative.  I want to go deep into the details, but I don’t want to bore.  And it’s gotta be funny.  Along the way, I expect there’ll be some swearing, cursing, and lots of frustration, but there always is when code, work, and life collide.

Why?  It’s probably something from my science upbringings, but I always like to question decisions, including mine.  First, I don’t think I’ve ever seen a job posting without “Excellent written and verbal communication skills” in it somewhere.  Second, and more importantly, communication is one of the keys to success in today’s global society.  And that’s that, not much to question.

Please enjoy, and I do so love feedback.