The Laws of Software Process

199

The Future of Software Development

frameworks for it. The author had included a primitive train and Hafsa exe-

cuted it. A “train” was a method associated with a model component

whose purpose was to assist someone in learning what the model did. In

the olden days, it would have been called “documentation” and it would

have been totally passive. Someone had described this to Hafsa.

“You have to read it, right, that I understand.” Hafsa had been puzzled by

the explanation. “But what does it do?” When it was explained that the doc-

umentation did not actually do anything, Hafsa was baffled why anyone

would include such a low-value artifact at all. This train was quite crude

but it did work. It ran through the syntax. Hafsa stopped a few times and

ran ...