I am asking the users of my decorator module if they would accept a new version breaking backward compatibility in a minor way.

Episode #12 closed my second cycle of Adventures. There will be a third cycle. However, now I have to write everything from scratch instead of translating from my original Italian series, therefore the publication rate will slow down. Here is some anticipation about the future.

I was visiting my friend Zack Urlocker and he did this 6-minute video interview for his column at InfoWorld.

Perhaps we only commit big chunks at a time as an artifact of older version control systems. What if we treated it as a full-fledged undo facility?

In this episode I discuss the utility of macros for enterprise programmers.

Floyd Marinescu asked me to organize an open-spaces session at the QCon Conference in San Francisco. I learned interesting things at both open spaces and regular sessions.

We recently moved "Python 3 Patterns & Idioms" from Launchpad to BitBucket. Here's why.

In this episode I will discuss the multiple evaluation issue, then I will show how macros can improve performance. Finally, I will give a practical example of how macros can be used to define a unit test framework.

A useful collection of observations about our profession.

Mark March 9-13 on your calendar.

Sun's focus on JavaFX has resulted in less progress on improving Swing development productivity. Has the shift of focus to JavaFX from Swing hurt the cause of client-side Java?

Yet another episode fully devoted to macros. I will discuss introspection, guarded patterns, literal identifiers, and a couple of common beginner's mistakes.

This episode is entirely devoted to Scheme macros from a personal point of view. Pattern matching is introduced as the fundamental mechanism on which macros are built.

Trying to do some simple file processing and strip blank lines, Andy stumbles through the "Ruby is supposed to feel natural" approach and just tries things. The conclusion - Python list comprehensions are still more flexible and powerful than any Ruby feature and inject is possibly the most misleadingly named function I've ever encountered.

Most build systems start out with dependencies, then realize they need language features and eventually discover they should have started with language design.