I'm now ready to beta test the "Thinking in C: Foundations for Java and C++" e-seminar, but I need a place that can handle the downloads.

Based on the success of last week's conference, I'm starting to plan the "Thinking in Java" conference for July. In particular, I need to set the dates.

A blog where Michael recounts a number of things that have happened to him this month that are likely of interest to no one but himself, and then finishes with something significant to show late respect for people who've read through the first part after being warned.

I continue to be amazed at how insanely great OpenSpace conferences are with so little effort on my part. Certainly, I provide structure, but most of that occurs in the first half hour and then I become a participant. As always seems to happen with OpenSpaces, I got so much more out of this event than I ever imagined.

The first in a series of articles about PyCon TX 2006, which marks my first blog entry in quite a while.

In his recent post, Bill Venners included a terrific quote from Ken Arnold. It crystallized my thinking on subjects as diverse as API design, interface design, and documentation (which many developers don't realize, is almost purely a design activity).

In his weblog, Peter Williams points out that Rails' default URIs are procedural, rather than RESTful, because they include an action name. I believe Rails' default URL scheme also puts the developer before the user.

Reviews of books on Ruby that I've either read or wish I could find.

While it may be attractive from the usability perspective to let users click on a link in an email to confirm a registration, it violates one of the cardinal rules of the web: don't change state on HTTP GET requests. This weblog post explains the problem and suggests solutions.

Ruby and Groovy are contrasted. Despite high hopes and best wishes for the Groovy project, in this author's eyes Ruby turns out to be the winner for most scripting tasks.

When I found Martin Fowler's article on the benefits of Rake (the Ruby version of Make), I immediately became committed to learning Ruby. I needed to write a mailing list program, too. Ruby turns out to be ideal for both.

In an article introducing Ruby on Rails' Active Record, Bruce Tate suggests that Java could enjoy some of the benefits of Rails by taking a wrapping rather than a mapping approach to persistence. I think this misses the point. What Rails really demonstrates is the benefit of code generation.

A quick observation on the difference between libraries and frameworks.

The reason for the radio silence on my part lately is due to me being hired by Microsoft! What does this mean for my other projects?

A response to Guido's discussion about marketing Python, and some observations about the issues that have come up.