Because the "Python 3 Patterns and Idioms" book project is distributed, I created a blog for everyone to give scrum-like reports. Did I just invent something?

I think the Smalltalk model was way ahead of its time. My vision is to move completely away from the idea of different kinds of storage.

Of course I'm asking the wrong crowd here -- you're watching the weblog. Still, you might have some ideas.

While I was in Brazil, I was interviewed for a Brazillian technical magazine, and the issue was just published.

Usage logs can provide useful inputs to user interface and web site designs. But all too often, naive interpretations of log data produce poor (or, at least, unsupported) design decisions. Here are a few of my concerns about the question, "What do the logs say?"

In this installment I will talk about tail call optimization, performance and the R6RS module system.

An attempt to answer the question - given 1 million lines of code in the repository (i.e. SVN), is there some rule of thumb as to the number of developers we have to keep on staff just to maintain those 1 million lines of code?

You know the bad feeling when you start looking at a Java code base that's just wrong. Proving it is something else again. Here's one way to show it.

Yet another introductory installment. However, after a brief discussion of the available Scheme bibliografy, I will actually start writing real Scheme code ...

In this episode I will talk about Scheme syntax, i.e. about the prefix notation and the infamous parenthesis(!)

SqueakNOS is an old idea that has gotten the kiss of life again. You want fast, simple, and OO? Check it out.

Just a heads up about three new libraries, and improvements in two established ones, ... (and a thinly veiled hint at some help from any members of the C++ community who have time, and a desire to work with highly efficient, highly robust libraries.)

If Python's what I want to do, I should write that book about it. Herein I muse about how to create a book relying largely on community input and help.

The response to arguments about self in Python is "explicit is better than implicit." In a discussion at Pycon Brazil, I realized that we do need self in the body of a method, but being forced to place it in the argument list is redundant. I'm not actually expecting it to change, but I want to try to establish that this isn't a dumb argument.

Brazilians are very warm and friendly, and PyCon Brazil in Rio de Janeiro had over 300 very enthusiastic and committed Python programmers.