Programming as Theory Building

by Peter Naur ยท 4 ideas

  1. Programs Are Theories

    A program is really a theory: the builders' shared understanding of how the system maps onto the problem it solves. The code and documents are only a partial record of that theory. Protect that understanding as your most valuable asset.

  2. Knowledge Not Written Down

    Much of what builders know about a system cannot be captured in documents: why things are the way they are and how to change them. It passes mainly by working side by side. Pair newcomers with the original builders instead of handing them a manual.

  3. System Death

    When the people who understand a system all leave, it is effectively dead, even if it still runs. Newcomers can keep it working but cannot change it well. Keep at least some people with the full picture on any system you rely on.

  4. Change with Understanding

    Changes made without understanding the system's design pile up as patches that work against it. Each one makes the next change harder. Before changing something, learn why it was built that way.

More on work