In one form, the question is "How do we handle the [X] transaction in the warehouse?" Another form of the question is "What do we do when [Y] changes?" The third form is less clear, but essentially the same: "How do we maintain [Z] in the warehouse?"

All of these …

Yes, it's an omission and, yes, it's a mistake. I should have said something along the lines of "risk is an uninteresting complication" or "risk is just a euphemism for bad management."

Why is risk uninteresting?

First, the seeds (Chad Fowler's "The Big Rewrite ", and CodeCraft, "To Rewrite or not …

In "It's Strategic -- but it's not -- but it was -- now it's a burden ", I rambled about the situation I encounter on a regular basis. Here's a Haiku that captures the situation.

Please Replace It

It's heavily customized,

We can't install an upgrade,

We don't dare touch it.

The maintenance costs …

First, I'm a pack-rat; I worry about deleting something valuable. Specifically, I worry about orphaned files because the application software is no longer supported or the media is obsolete.

For example, my resume is a Hypercard stack. Really. Hypercard is an OS 9 application, and future OS X's won't support …

Here's what I observed.

Customer: "Our business performance isn't what we want. We think some of our intranet is no good."

Us: "We'd love to look at it."

Customer: "Not so fast. You can't 'look at it'. You have to propose a measurable change in business performance, define a fixed …

To begin with, we're talking about the implementation's source code. Here's the situation: Ann says that Bob's code is no good, and she's provided an alternative implementation. How do we choose?

The first part of any scorecard is the SEI Quality Measures Taxonomy . It's marked "Legacy", but I haven't seen …

While there are lame reasons for using XML, there are good reasons also. The good reasons, however, aren't delightfully clear. They seem to be clouded by the lame issues. I'm trying to sort out the best and most logical reasons for using XML.

Here are 8 typically lame reasons for …

I read "Stamp on the ants ", which lead me to write "XML - One Ring to Rule them All... " because I'd seem some remarkably lame justification for XML. I saw an interesting response in "XML is first class, scripting languages are second class ".

At this point, we have an interesting tangential …

I harp on Design Goal 6 in the XML 1.0 Standard , "XML documents should be human-legible and reasonably clear". In Kontrawize, the response is XML editors help meet this design goal. "There are plenty of good XML-aware editors around, some of which are free." While true, I think this …

The XML folks seem to have a number of points:

• Ant already works. Complexity be damned.
• XML is fine for everything that's not Java. Except SQL. And CSS.
• Ant is "already" part of the technology stack, and it uses XML. Anything better isn't already there.
• Everyone already knows XML. They …