"I've had this conversation with architects and city planners and they all say this."
Now you are having a conversation with one who isn't.
The analogy between architectural patterns and software patterns is more akin to the way in which software patterns are not relevant to an application programmer in regards to the structure of black boxes such as third party libraries or the OS kernel. Architectural design depends on OPM (other people's money) to execute.
Urban planning not writing a web app. It's maintaining legacy spaghetti code in within an institution with entrenched interests. Brasilias only come along every hundred years or so, and your average joe doesn't get appointed. But just about every one of the major urban planning patterns is standard consideration in most contemporary municipal planning departments [in the US]. Politics and money of course tend to have an influence over outcomes, of course.
On the architectural side, a lot of A Pattern Language is not directly applicable to most architectural commissions because it is focused on domestic architecture rather than commercial. Banks don't offer a place to apply, "The couple's realm."
Incidentally, complaining about the impact of building codes has probably been going on for nearly FOUR millennia.
Yes, I agree with you. I actually didn't have software in mind when I wrote my post, but the differences you note are important.
Planning is indeed a mess. However, there are 'breaks' between 100-year plans and building-scale architecture such as neighborhood development, block-level revitalization projects, etc., which don't offer a greenfield opportunity but do allow a planner to make some important choices. Ideally, well-designed rooms would create an opportunity for homes, clusters of homes, streets, clusters of streets and business districts, and up and up. Obviously it is unlikely.
The reason it's unlikely is the patterns are so opposed to how things are done. You mention the bank. Commercial is actually addressed, but there is no place in Alexander for an isolated, cold, commercial bank branch that requires a commute for its employees. Alexander's vision for our work is too radical to happen right now.
Now you are having a conversation with one who isn't.
The analogy between architectural patterns and software patterns is more akin to the way in which software patterns are not relevant to an application programmer in regards to the structure of black boxes such as third party libraries or the OS kernel. Architectural design depends on OPM (other people's money) to execute.
Urban planning not writing a web app. It's maintaining legacy spaghetti code in within an institution with entrenched interests. Brasilias only come along every hundred years or so, and your average joe doesn't get appointed. But just about every one of the major urban planning patterns is standard consideration in most contemporary municipal planning departments [in the US]. Politics and money of course tend to have an influence over outcomes, of course.
On the architectural side, a lot of A Pattern Language is not directly applicable to most architectural commissions because it is focused on domestic architecture rather than commercial. Banks don't offer a place to apply, "The couple's realm."
Incidentally, complaining about the impact of building codes has probably been going on for nearly FOUR millennia.
http://en.wikipedia.org/wiki/Code_of_Hammurabi