I still mull over his comment about the role of "architect":
> Between 1830 and the Civil War, architects published scores of pattern and style books. At one point or another, most of those volumes argue that an architect offers the client protection from the builder. The case is often founded on social class, the architect being the client's ally by virtue of education and breeding. The argument plays upon the suspiciousness of clients about builders, a wariness that seems to have been around for so long that it probably deserves to be called natural.
I can't help but apply that class interpretation to the roles of "architect" and "developer" in a software project.
> Between 1830 and the Civil War, architects published scores of pattern and style books. At one point or another, most of those volumes argue that an architect offers the client protection from the builder. The case is often founded on social class, the architect being the client's ally by virtue of education and breeding. The argument plays upon the suspiciousness of clients about builders, a wariness that seems to have been around for so long that it probably deserves to be called natural.
I can't help but apply that class interpretation to the roles of "architect" and "developer" in a software project.