This episode goes in depth through the most obscure secrets of Scheme, by exploring the (Dark) Tower of Metalevels of the R6RS module system.

Last week my MacBook died of a premature death at age 2. Out of necessity, I have been forced to borrow my wife's EeePC for a while and to use it as my main development platform. The unexpected thing is that it just works perfectly.

Both social networking and votable newsfeeds are one-dimensional. Combine the two and you get a kind of Pandora for stories, and for discovering people who like the kind of stories you do.

An interview with InfoQ; also includes what I've been up to: writing, theater, conferences, management issues, painting, "First Steps in Flex," opinions on web development, and "Thinking in Java."

In this episode I introduce the concepts of implicit phasing, explicit phasing and multiple instantiation of modules. Moreover, I discuss various portability issues of the R6RS module system related to the different phase separation concepts.

One of the trickiest things about Scheme is the distinction between the interpreter semantics which is typically (but not always) used at the REPL and compiler semantics which is typically (but not always) used in scripts.

A science-fiction study for an upcoming writing group meeting. However, I honestly believe this could happen, and happen in a way similar to what I describe here.

In the world of animation, Apple's web page is "lagging". It's an interesting example of how not to depict a real time event stream in a non-realtime environment.

I finally figured out the right analogy for software development. Alas, the target audience for this analogy won't be happy with it.

This is the first of six episodes concerning the R6RS module system. The module system is quite new and it is the result of several compromises. As a consequence, it has some rough edge and writing portable code - specially for macro writers - is not always trivial.

The Internet accelerates everything. We now watch companies go from "the next great thing" to "meh" in the space of a few short years.

Retrospectives allow you to analyze what worked and what didn't about a project so you can do better in the future. How often, though, do people have either the resources or the wherewithall to do a retrospective on a complete disaster -- arguably where we'll learn the most?

Some notes of my own, and some collected from other attendees.

Early registration ends June 2.

In this final installment I show a solution of the design problem posed last week, i.e. I show a possible mechanism for adding multiple interfaces to an object without polluting its namespace with mixin methods.