This is a modern nail clipper. It was invented, it appears, by Chapel Carter in 1896. Ask yourself, which elements of this object reflect design, and which elements represent architecture. I am going to offer a fairly clean distinction for you to ponder, but I’d like you to make up your own mind first. You don’t have to be a mechanical engineer or any sort of engineer, architect, artist or designer to answer. Just go with your intuitive sense of those terms, and apply them. These ideas also apply to organizational and social design and architecture.
This piece grew out of an interesting bit of crossfire on Twitter a few days ago. It began when I said:
“Am realizing I enjoy design, but not architecture. Design is the ‘play’ subset of ‘architecture.'”
This provoked an instant response from @jrdotcom, a software guy I know:
@vgr In software, there is no difference between design & architecture. They are just words that non-programmers have invented.
After a bit of back and forth thesis-antithesis, another guy I know, @jbsil01, also a software guy, offered a partial synthesis:
@vgr as a programmer, design can mean the same thing as architecture. as a user, architecture should be irrelevant to design.
Reflecting on the exchange, I realized that all three positions bother me. My own remark is too flippant, clearly. But @jrdotcom’s position, that there is no substantive distinction, that this is all pointy-haired-boss-speak, at least in software (and I have heard similar views from other sorts of engineers) is too dismissive of the importance of language. And finally, @jbsil01’s reliance on subjective user experience as a fundamental filter to tease the two apart is too pragmatic and operational. So let’s dig deeper. I’ll frame my discussion in terms of engineering, but this applies, mutatis mutandis to other synthesis fields which mix utilitarian intents with aesthetic ones.