Back in the olden days (ca. 1981) Barry Boehm's Software Engineering Economics provided a detailed and definitive guide to estimating. It did one really important thing: it provided a conceptual model of software development that had a (relatively) focused set of degrees of freedom, an input driver and a couple …

When approaching reverse-engineering, we have to partition the big puddle of code into some useful pieces that we can manage intellectually, and will likely become parts of the resulting application. In some cases, this is either impossible or valueless. It may be that the application is so hopelessly bad that …

In order to talk about what goes in the database, we need to put the question into some kind of useful context. Weirdly, the question came to me in a context so twisted and bizarre that it's a little hard to sort out what -- precisely -- was going on. First, what …

A taxonomy of pipeline alternatives is a big, hairy deal, involving lots of alternatives. While your basic API methods are relatively few in number, each language and platform introduces new options. Without some focus, it's challenging to produce a big, fluffy description of all potential alternatives.

However, the interesting thing …

When I was a kid, reverse engineering a legacy application was a challenge. Tools were non-existent, and even a civilized practice like unit testing didn't really exist. Now that we have test driven development, I think we can apply this to reverse engineering the billions of lines of legacy software …

This is not a Python to the rescue story. This is a true, deeply horrible situation. I was rescued by a reframing technique I'll call Extraction.

First, the function had nested if's without enough else's -- the kind of thing that handles two of the four possible conditions.

if( a ) {
    if …

Why Python, indeed?

"It's clear that you find it easier and quicker to use Python, and that's fine. It's often quickest for people to use the tools that they know best."

As they say on Fark.com, "This".

However, the Python advantage doesn't stem from knowing Python better than Java …

I find the value proposition for a Service Oriented Architecture to be agility and simplicity.

See Linthicum's Real World SOA blog postings, specifically "Core Value of an SOA... " Here's the interesting quote: "this does not mean that reuse is not a core value of SOA, but its value is much …

My experience is that an SOA has the potential to be cheaper and simpler. However, cheaper and simpler may not be the only value proposition.

Kontrawize says: "there is only something to gain with SOA for the parts of your software that genuinely have re-usable functionality, and are expected to …

It's about 10,000 lines of C. Much of the C is focused on "framework" issues -- logging, synchronization, parsing the parameters and that kind of thing. In this case, it appears to be 30-50% of the original C code is stuff that is available in Java and can be removed …