Engineering

The Title Trap asks: what are we actually paying for? This essay answers it by defining three substantively different practices in knowledge work. The problem is not that people use “engineer,” “technologist,” and “technician” interchangeably—it is that we have made it impossible to call anyone anything else. I. The Profession That Lost Its Names In medicine, the distinction is clear and enforced by law. An MD and a Nurse Practitioner are both valuable. Both are trained professionals. They are not interchangeable. They have different training, different scopes of practice, different liabilities. The system is designed so you cannot confuse them. …

The word “engineering” was applied to software deliberately, not descriptively. At a 1968 NATO conference in Garmisch, computer scientists chose the phrase “software engineering” as a provocation—an aspirational demand that the discipline impose on itself the rigor that physics imposes on civil and mechanical work. The word was not a recognition; it was a challenge. Fifty years later, the challenge remains unresolved. And the discomfort that trained engineers feel when they move into software—the sense that the ground is somehow less solid, the rules more negotiable, the stakes harder to calibrate—is not a failure of imagination. It is a correct perception of something genuinely different. …

The lathe doesn’t tell the machinist where to put the shaft. The oscilloscope doesn’t tell the electrical engineer where to route the signal. The crane doesn’t tell the civil engineer where to put the walls. Every mature engineering discipline figured this out early and never looked back: the physical problem drives the design. The tools are means, not ends. Software was the exception — and for a remarkably long time. …