The Engineer Who Prizes “How” Over “Why”
Many people get stuck early on the question of “why?” — why build this, why pursue that path. The question can paralyze. But there are others who bypass it entirely. They care about the “how?” — the mechanics, the craft, the execution. For them, any rationale suffices as long as the work is interesting. Dennis Ritchie belonged firmly to this second group. A gifted programmer, he found his satisfaction in the doing.
Today, the reasons for Unix and C appear self-evident. Unix underpins the file systems, the internet, Windows, Mac OS X, Linux and the software freedom movement. C gave rise to C++, Java, Perl and Python. The lineage is clear. But in 1972, nobody, not even Ritchie himself, could have articulated those justifications. The honest answer to “Why Unix?” or “Why C?” back then would have been something like “for space travel” or “for fun.”
Code as an End in Itself
Ritchie helped normalize the idea that a programmer could work for the sake of the craft, not merely as a servant to some larger purpose. A developer could write code as an expression of art and skill, without feeling the need to justify it through utility or scientific necessity. Making something should be reason enough.
Seen this way, his work has an artistic dimension. It takes an appreciation of elegance to understand the universality of Ritchie’s achievements. Unix and its file system are not transient artifacts; they are lasting abstractions. The file system, in particular, stands as one of the most durable concepts in computing — and understanding why remains essential for anyone serious about the field.
The Legacy of the How
Over the decades, the influence of these creations has reshaped how engineers think about their work. The lesson from Ritchie’s career is that the “how?” can lead the way, and the “why?” often follows behind — a reversed relationship that many disciplines take for granted today.
