Architecture is so important that everybody has to have it in mind all the time and to think that we can take the responsibility for good architecture and concentrate it in one individual is the real mistake.
Ward discusses how patterns come about and how we begin to recognize them in our own work.
The nice thing about a pattern is you take that something everybody knows how to do and you give it a name; and a lot of people look at it and say “I knew how to do that only I never called it that.”
He also talks about the problems with the lone developer paradigm and why the social interaction of paired programming in XP allows for a faster communication between developers. He further shows how this communication is similar to defining a pattern.
I do know that a lot of times if the programmer gets good; while he is getting good, he learns that most people do not understand what he does. So that’s really separating for programmers. Programmers are kind of driven apart by that realization that they are dealing with things that most people do not understand and after a while they give up trying to communicate.
Watch the entire interview with Ward Cunningham.