I have had side projects for as long as I have been writing code. Whether it was some overly idealistic goal of being like another Linus Torvalds ( I wanted to make my own operating system ) or something a little less ridiculous as making a pop3 server from scratch, I have always scratched that itch.

As I soon found out, having side projects had an additional benefit: I was able to command a much higher salary ( due to the newfound experience ) as I went from job to job.  Employers didn't care where you got the experience just as long as you could do the work. Consulting companies liked it too.. you weren't training on their dime either.

The real reason I have side projects is that I still love to write code. Not writing code for writings sake, but rather writing code to express an idea or to solve a problem. To see that idea morph from something that is nebulous in your mind into something that you can show to other people.  To create something out of nothing just really appeals to me.

For years of starting new side projects, I can honestly say that I have completed one project.  This blog is that completed side project.  No software is truly complete, but this blog is complete enough to achieve the goals that I initially set out for it.  It is functional, I use it on a regular basis and I have learned a bit about python and django.  Most importantly I have learned how to complete a project with a minimum amount of time and effort.  With having a side project, you set the deadlines and the pace.  You have the opportunity to try out different practices to see what works best for you.

Since this post is already a bit lengthy, I'll close out by saying: It's pretty damn cool to be using software that you create for yourself, try it sometime you might like what you come up with :)