Now that I've covered the basics of monkeypatching, it's time to dig deeper.

When you monkeypatch a function, you're limited to accessing the function's parameters and other data in its global scope. This article is an introduction to one way that you could access data in the calling function's local scope.

Monkeypatching is a common word among Python programmers. But what is it?

This post is an introduction to monkeypatching.

pelican_precompress 1.1.1 is now released and features faster compression times.

Remember that one time when your software requirements changed and you realized that you would have to make dramatic changes to your code? Remember how that's only happened to you once?

I've been working on the same codebase for eight years. During that time I've learned that requirements change, and I've slowly learned some design patterns that can help make code flexible enough to accommodate changing requirements.

I'd like to share some of those experiences and lessons with you.

Hynek Schlawack posted an article titled "Why you should document your tests". I think that you should document your individual assertions, too.

I've added an XML sitemap to the site.

I've recently discovered the joys of JSON output from CLI apps.

I imported all of my ancient Wordpress blog entries (2004-2007).

I added a robots.txt file so that a common request won't be greeted by a 404 page.

I've set up HTTPS and redirection for www.kurtmckee.org, and I've enabled automatic certificate renewal.