Some cleanup efforts lead us to a theoretical idea, and to a successful spike. Out of chaos, order.

There’s this hack where we return the elements of a set as if they were sets. Nothing like theory to fix a hack, is there? Naturally there are some stumbles along the way, mostly involving the tests. Remember who you’re dealing with.

I did an offline experiment to figure out what to do about this :each thing that returns two items instead of the usual one. Based on that, we’ll create a new little object, wire it in, then clean up the tests a bit. Join us …

Just for a little something to do, let’s add iteration capability to our XSets. [Added: Clarification of something that threw at least one reader off.]

A small experiment, implementing “restrict” in Ruby. As usual, warts and all.

Some friendly folks have been making suggestions and asking questions. I’m still in the mode of figuring out what to do and how to do it. For those who are interested …

For some reason, I’m thinking — at 2 AM — about Extended Set Theory. An interesting topic, to me, even at this hour. But should I build something? I don’t know; help me out.

It seems like every development project begins with the date, and we’re held responsible for “making the date”. Making the date is a management responsibility, not a development responsibility. Here’s why.

Updated with cool cartoon from Simon Baker.