I use Markdown for most of my online writing, and also as the format for most of my personal notes. Since I also use Graphviz quite frequently, adding an extension to handle both seemed like a reasonable next step.
Spent a bit too much time this weekend trying to implement a stack-based Markdown interpreter in Erlang, and not quite enough time in the planning process. That said, it was a nice initial sketch, and in a few days I'll have time to rework it accordingly.
Programmers talk about DRY, or Don't Repeat Yourself, all the time. Its a strategy for making programming more pleasant, more efficient, and to reduce errors. LifeFlow uses a simple idea, which I have brazenly labeled Dynamic Blog Context, to try to take a few steps toward DRY while writing blogs.
A look at extending the Python Markdown library. It happens to be an extremely well written library, so extending it is a bit more fun than it ought to be. Take a look.
Recently I have run into a few situations where I really wanted to avoid Markdown messing with segments of text, and there isn't a completely intuitive way to deal with that by default, so I put together a quick solution. And.. while I was at it I added some support for rendering Textile and ReST from within Markdown as well.
After some additional work, erlang_markdown is cleaning up fairly well into a usable package. At this point, pretty much all of Markdown should be implemented outside of the alternative header syntax.
Software engineer, technical leader, sci-fi reader, and so on. Born in NC, living in SF, and glad to grab a coffee.