I seem to visit more and more sites where the pages don't render right, to the point of being unreadable and unusable. And they're trying to sell me something! Why is this happening?

I was recently quoted in an article, and need to correct and attribute the idea.

My previous post led me to this library, which appears to solve the coarse-grained parallelism problem quite elegantly.

I'm glad to see the first beta of the so-called Python 3000. But for a version that's supposed to break all the rules to become better, I'm not seeing what I think is most important.

Some people have told me I'm a brilliant marketer. Eventually I realized that I just stumbled into pieces of good luck a couple of times.

In Java Posse #136, the Posse discusses the Google Singleton Detector which automatically discovers singletons in your code and they all agree that singletons are a bad idea.

As Joe Nuxoll of JBuilder and JavaPosse fame will tell you (given the slightest provocation), one place where the Java designers completely dropped the ball is in Java's component model. This becomes especially clear when comparing it with a system like Flex which has full language support for components.

As promised, everyone moved their knowledge forward, and I personally felt like I turned a corner in my understanding; something clicked and came together.

We've decided to hold the RIA conference at a later date. Instead, you can now extend your Flex and AIR experience for an entire week.

I received a message asking about how to decide whether to port to a new language first, redesign first, or do both at the same time.

August 15-17 I will be holding an OpenSpace conference to discuss the reasonable distribution of an application between client and server, with emphasis on the return to Rich Internet clients.

August 13-14 I will be holding (with James Ward of Adobe) a Jam on Flex and AIR (Adobe Integrated Runtime, formerly called Apollo).

Combine the power of Python with the polish of Flash to create a desktop application. This approach will also work with any language that has support for creating an XML-RPC server (Java, Ruby, C++, to name a few). Also, The XML-RPC server can easily be on another machine.

I'll be doing a new experiment for this one: hiking in the morning instead of the afternoon.

In Jerry Weinberg's classic "The Secrets of Consulting" (Dorset House, 1985) he says something to the effect of "You probably won't be able to make any changes."