I've been trying to help some folks who have a "search" algorithm that's slow.

They know it's slow -- that's pretty obvious.

They're -- unfortunately -- sure that asyncio will help. That's not an obvious conclusion. It involves no useful research. Indeed, that's a kind of magical thinking. Which leads me to consider …

Check out this picture.

http://www.petapixel.com/2011/12/27/what-5mb-of-storage-looked-like-in-1956/

Here's a great summary of Agile techniques. It's in ComputerWorld's Development section, in an article by Heather Havenstein: "Five Web 2.0 app dev lessons for enterprise IT ". I think the article is mis-titled, since it's basically "Agile for Big IT."

Some of the five techniques are motherhood and apple-pie …

Centuries ago -- it seems -- Jim Coplien facilitated a session for us at ChiliPLoP . Eventually, I figured out that patterns are a solution to a problem in a context which resolves various alternative forces, and has some understood consequences. Context - Problem - Forces - Solution - Consequences.

In this month's CACM, the article on …

In Object Modeling , I repeated a procedure for object identification that comes from the classic Object-Oriented Modeling and Design (Rumbaugh, et. al.)

Objects are characterized by their state change. Therefore, to distinguish among classes of objects, we need to determine if two objects have the same states and state transitions …

Without mentioning Armour's The Laws of Software Process: A New Model for the Production and Management of Software (which includes the Five Orders of Ignorance, quoted by Paul Freedman in "Uncovering Ignorance in Software Development "), Purdy has hit the nail on the head regarding gestation of architectures.

Is Gestation overhead …

One of the best ways to avoid problem solving is to treat the problem as fluff. Often, our users begin the conversation with this assumption, and we play along. Other times, we make this choice because we're just too lazy (or negligent) to make an effort.

Here's how it plays …

The deployment document describes an installation of the system, with specific host names and addresses. This document is the last of the formal deliverables, and forms the basis for an operator's or user's guide.

The deployment follows successful implementation of the design, based on the architecture and requirements.

An implementation document is prepared along with the software to present the packaging and component structure, including visible interfaces of components. This shows the structure of the final deliverables, and describes the files, databases and other persitent features of the system. This document will also identify all third-party components used …