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 parentheses(!)

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.

Having the computer help you write and maintain your code is an essential facet of successful software development, and all good consultants will recommended that you follow suit. (Even if, sometimes, they forget to do so themselves ...)

Scheme is a language with many implementations and with few libraries. In this episode I will discuss the current situation and I will give some useful indication to the Scheme beginner.

This is the first episode of a long running series of articles about Scheme. Currently I have published the first 11 episodes of it on Stacktrace. This episode is a revised translation of http://stacktrace.it/2008/02/le-avventure-di-un-pythonista-schemeland-1/

Once the boilerplate traditionally associated with the Service Locator Pattern is eliminated, one of the key motivations for Dependency Injection is reduced, if not eliminated. This article, the second of a two part series, looks at the pros and cons of each approach to interacting with services.

Traditional implementations of the Service Locator Pattern result in a large amount of boilerplate code. This article, the first of a two part series, shows that this is not a necessary weakness.