I've always been a full-time software developer, and the majority of the code I write is owned by my employers. My wife occasionally allows me to hack on personal projects after she goes to bed, and I try to make most of it available online.

I keep my public projects and open-source code available on a few different repositories:

  • bitbucket:

    mercurial repos, preferred for new development

  • github:

    experiments with git, forks of other projects

  • google code:

    older svn projects

If you're here, you might be interested in one of the following projects:

If that don't do it for ya, I leave you with this inspiration:

>>> import this
The Zen of Python, by Tim Peters

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!