← @bgSponge

"Programming as Theory Building", P. Naur (1984/85)

Summary

Peter Naur's 1985 Microprocessing and Microprogramming essay, from his 1984-08-28 Euromicro 84 keynote in Copenhagen, treats programming as the work of building a tacit theory of how a real-world activity is matched by program execution.

  1. The theory lives in the programmers.

    They must know how the world maps into the program, why each part is there, and how a new demand resembles what the design already handles.

    the proper, primary aim of programming is, not to produce programs, but to have the programmers build theories

  2. Documentation cannot carry the theory.

    Group B had the compiler text, annotations, and design write-ups, and still proposed patches that wrecked the structure Group A could repair on sight.

    the full program text and additional documentation is insufficient in conveying to even the highly motivated group B the deeper insight

  3. A program dies when its team dissolves.

    Execution can continue. Intelligent modification cannot. Rebuilding the theory from the text is strictly impossible and often more expensive than a new solution.

    The death of a program happens when the programmer team possessing its theory is dissolved.

    program revival, that is reestablishing the theory of a program merely from the documentation, is strictly impossible.

  4. Cheap edits are a text-production fantasy.

    Flexibility has to be designed and paid for in advance. Patches that are behaviorally correct still decay the program when they ignore the theory.

  5. Methods cannot sequence theory building.

    A theory has no inherent parts or order. Familiar model solutions help, but the programmer chooses techniques. That makes programmers irreplaceable professionals.

Read the original ↗Save to your Sponge

Summarized with Sponge. Quotes are the author’s own words.

More from @bg

All readings →