Blogging Roller

A couple of people have asked me if Roller helped me to land my new job. I'm happy to report that the answer is yes, Roller helped. I'll explain that, but first, realize that when I say "Roller" I mean a number of different things. When I say Roller I mean developing the Roller software, writing the Roller article for O'Reilly, participating in the Roller project, and writing for my weblog.

I must admit that I was a little worried that Roller might hurt my chances of getting a new job. I was concerned that an employer would see Roller, my weblog, and my writings as a diversion that would keep me from getting real work done, or, that some potential employer would read my weblog and either strongly disagree with something I said or decide that I am only rambling nut-job. That is only one small part of my personality. Those who know and love me know that I am much, much more than just a rambling nut-job.

Roller helped me out in several ways. Roller gave me experience with and knowledge of new software development technologies, techniques, and tools. I wouldn't have Struts, Velocity, XDoclet, Castor, and Hibernate on my resume if not for Roller. I also learned a lot about software project managemement including source code control, release management, issue tracking, developer/customer support, etc. This is why I listed Roller on my resume and gave it equal billing with my other previous jobs.

Roller also me exposure, but more importantly Roller exposed my code, my writing, and the ways that I work with others. My new employer did not find me via my weblog, but once they did find me they were able to download and review my code, read my technical writings, and could even have searched the Roller mailing list archives to see how I interact with other developers and end-users of my software.

Roller was certainly not the only factor, as I do have a strong resume even without it, but Roller was an important factor in landing the new job.