A Day in the Life

A day in my life. Thoughts on leadership, management, startups, technology, software, concurrent development, etc... Basically the stuff I think about from 10am to 6pm.

4/27/2006

Business: The Engineering Value of Blogging

Over on JobSyntax blog, Gretchen talks about the role of blogging in recruiting. She has linked in several articles and recruiting blogs where the subject has been discussed.

I’ve come to the conclusion that software engineers must blog just to be competitive. And that we need to share not only knowledge and code samples, but also our thoughts on technology and our experiences. This makes it easier for prospective employers to say, "Yes! I want you." And for our peers to say, "Your post on X saved my project." Our peers are really our audience; future employers just get the benefit of our conversation.

Every time we walk into a job interview both the candidate and employer are selling to each other. And selling is about telling stories and reducing risk. Each side tells their story and asks questions that make them feel safer in saying, "Yes." An honest and open approach to blogging can eliminate the marketing feel of a blog and can clearly communicate your "story". A story that shows you for who you really are and that allows the other person the opportunity to feel safer (reducing their perceived risk.)

An engineering blog should demonstrate knowledge, coding style, and relevant technical experiences. But it will also demonstrate writing ability, communication style, humor, clarity of thought, and in some cases, the other faces we wear. All of these qualities are very hard to determine from traditional resumes and cover letters. And even during the interview process it can be difficult to get a clear picture of a candidate’s "style". A well tended professional blog helps with all of that. It makes us 3-dimensional and real. All of that makes us more marketable and easier to sell.


2 Comments:

At October 17, 2007 12:28 PM, Anonymous Anonymous said...

This is a great point. I have considered this and have been maintaining a private blog doing just what you say but I am hesitant to make it public. The reason is, it is difficult to keep proprietary knowledge private. Also, my co-workers might might easily be offended by my sharing a lessons learned that involved their mistake if they make the connection. These seem to be the topics that I am compelled to write about most often. Any thoughts on this?

 
At February 21, 2014 9:28 AM, Blogger Shawn Kirsch said...

totally agree with this.

 

Post a Comment

Links to this post:

Create a Link

<< Home