Since I spend a lot of time on skill upgrades for my clients, my books are oriented around that theme. It's something that I learned from Jim Bullock : there's a Clue Absorption Rate, and you can't exceed that rate. These books are about building skills incrementally.

I've got three Python-related …

I think that learning Java is challenging. You've got to learn the language, object-oriented programming, the libraries and the endless Java Technologies. The Java landscape is crowded with J*tx* and tx J add-ons, where tx is some technology abbreviation; for example, JAXWS, JAXB, SAAJ, JMS, JFC, JCE, JAAS, etc …

Thanks to everyone who attended. See Designing Web Services with the J2EE(TM) 1.4 Platform : JAX-RPC, SOAP, and XML Technologies for more information. Also, check out Dr. Dobb's SOA, Web Services and XML department.

Here's the Micro$oft PPT file: Web Services 8.ppt

Here's the Open-Office file: Web …

Here's the shocking result.

http://www.bbspot.com/News/2006/08/language_quiz.php

And I thought I was just arrogant. Now I see that it's worse than I thought.

There are a number of necessary skills for being an architect. Here's a list of four that occurred to me as I tried to piece together a coherent thought from a flurry of emails.

• Summarize.
• State A Goal.
• Know The Technology.
• Manage Your Investment In Learning.

These aren't sufficient skills …

First, I'm really pleased to see a focus on end-user applications of Python. It seems like most of the Open Source Community likes to build infrastructure, operating systems, servers, frameworks and components. Maybe I'm looking in all the wrong places, but I have a soft spot in my heart for …

The points are serious issues. However, the best summary comes from Karl Guertin: "My explanation is that Duck Typing is like Ethernet, in theory it will break, but in practice it works pretty well."

There were three questions which raised four issues. The questions included the seemingly incomplete OO implementation …

In one case, the prospect had 7 interlocked databases, and wanted to do a technology upgrade. In other cases, the numbers was larger (up to 30, I think) but the problem was the same.

Essentially they said "It's taking us forever to rework this design. What should we do that …

Once I learned C++, all my C programming became poor-man's OO.

• Every "class" became a C structure type.
• Every class structure was implemented as a header file that defined the structure and a bunch of method functions.
• Each method function would have a "self" argument, which was a pointer to …

In a recent code review, I saw a bizarre habit. The author defended it so vehemently, I gave up on trying to explain the needless confusion it caused. The author was one of those "I always do it this way, and I'm always right." people, so nothing was gained by …