This text is less “technical” in the algorithmic sense and more methodological: what it means to treat program design as a systematic activity, in a world where complexity grows faster than our capacity to keep it in mind.
What interests me here is the fine line between what can be formalized (and possibly automated) and what remains inevitably human judgment: choosing a decomposition, evaluating trade-offs, constructing a coherent explanation of the solution.
Behind the discussion lies the same theme of the decade: “order” does not come from a recipe, but from well-chosen intermediate objects and controlled transformations. Any serious method needs a form of external memory of the project — an intermediate form — and a set of criteria that keep it coherent.
Viewed in context, the article functions as a bridge: between formal modeling (1981–1983), the instrumentation of the method (1985), and the realization of an environment (INTERFORM). It is my way of saying: design can become systematic without becoming mechanical.