The programmer as navigator

Abstract

This paper takes a new view of the familiar title. It is argued that a computer program may be viewed as a map, and the programmer as a cargo-laden vessel navigating the routes. Two programming case studies are presented to show that, even where the map itself is well structured, hazardous journeys may result from the overloading of the vessel with directional cargo.