3 ms·

I expect CA was as surprised as anyone when the GoF cargo-culted his ideas into OO software development. So far as I'm aware he never claimed any particular ex

I expect CA was as surprised as anyone when the GoF cargo-culted his ideas into OO software development. So far as I'm aware he never claimed any particular expertise or experience in software in any of the original books. The equivalent would be architects taking the design principles of Multics and using them to lay out buildings. That would be a bizarre thing to do. And it's no less bizarre in the other direction. What seems to have happened in practice is that the GoF used CA's work to give their own ideas about patterns in OO software development more credibility than it would have had otherwise. It's not that the idea of OO patterns is inherently bad. But pretending that it's somehow genuinely based on some speculations about built architecture is neither convincing nor credible. Having said that - the CA quote above makes perfect sense, and it is about beautiful software from the end user's POV. Which is a view that's often missing from CS and developer culture in general. Typically there's more effort put into forcing humans to act in bureaucratic, corporate, and computer-constrained ways, than in forcing computers to behave in ways that are inclusive, accessible, ecologically stable and robust, and organically open-ended.

eternalban 4y ago
I suppose we can ask GoF authors if they needed credibility boost from an obscure (certainly in CS circles) architect. The quote does not make any coherent sense, it's a sentiment decorated with buzzwords. As I said, if Alan Kay wants to hand wave CS utopia, heck, the man has certainly earned it, and his woowoo talk is actually intellectually far more densely packed and nutritious. Btw, I said nothing about patterns, OO, good, or bad. We also disagree about portability of concepts and viewpoints across disciplines. I studied architecture in grad school and engineering before that. And learning C/S via vocational route I found my EE and architecture background was beneficial and definitely informed my architectural thinking in software. I merely said you can not have a one-to-one mapping. Here an example: modular thinking -> engineering, architecture, software. But "Pattern Language" on its own is not fully informative of conceptual concerns of software architecture. That was the point.
- auggierose 4y ago
  I think Christopher Alexander (CA) absolutely got the right impression. You don't seem to have watched the CA talk. You probably should. He is not claiming to know anything about software engineering, but he describes what it should achieve, from his "ignorant" point of view. And I will gladly use some of his design insights in my software from now on, and see if and how I can apply them.
  - eternalban 4y ago
    You are right, didn't watch it. Will do.

eternalban 4y ago

I suppose we can ask GoF authors if they needed credibility boost from an obscure (certainly in CS circles) architect. The quote does not make any coherent sense, it's a sentiment decorated with buzzwords. As I said, if Alan Kay wants to hand wave CS utopia, heck, the man has certainly earned it, and his woowoo talk is actually intellectually far more densely packed and nutritious. Btw, I said nothing about patterns, OO, good, or bad. We also disagree about portability of concepts and viewpoints across disciplines. I studied architecture in grad school and engineering before that. And learning C/S via vocational route I found my EE and architecture background was beneficial and definitely informed my architectural thinking in software. I merely said you can not have a one-to-one mapping. Here an example: modular thinking -> engineering, architecture, software. But "Pattern Language" on its own is not fully informative of conceptual concerns of software architecture. That was the point.

auggierose 4y ago
I think Christopher Alexander (CA) absolutely got the right impression. You don't seem to have watched the CA talk. You probably should. He is not claiming to know anything about software engineering, but he describes what it should achieve, from his "ignorant" point of view. And I will gladly use some of his design insights in my software from now on, and see if and how I can apply them.
- eternalban 4y ago
  You are right, didn't watch it. Will do.