He had really interesting computational ideas about harmony. From The Nature of Order (2002) “As architects, builders, and artists, we are called upon constantly—every moment of the working day—to make judgments about relative harmony. We are constantly trying to make decisions about what is better and what is worse…” Following this, he published a paper on “harmony-seeking computation” as an approach to optimize “wh…
Christopher Alexander has died
91–100 of 139 posts
Re: Christopher Alexander has died
#92Earlier quoted context omitted.
I wouldn't call it love per se , but it certainly does take a special kind of empathy to put yourself in the shoes of someone using your software, and to use that perspective to make a great product.
I have several junior developers on my team who came from the customer success / support side of the business who grew themselves into developer roles. They typically have not only the strongest desire to learn & improve, but also the most empathy and understanding of our impact on customers & their livelihood.
Re: Christopher Alexander has died
#93I had no idea Christopher Alexander was a software development luminary. I knew him via _A Pattern Language_, and I'm way more into architecture and physical space design than I am software. Now I'm mega interested to absorb his thoughts on software. I expect I'll be much better for it. He's on my "recommended reading" list, I had _no_ idea he was so enmeshed in software: https://josh.works/recommended-reading#a-patt…
It's not so much that Alexander has thoughts on software but that others realised they could draw clear analogues.
Re: Christopher Alexander has died
#94Re: Christopher Alexander has died
#95Saw him speak at Berkeley around the time his book on the Eshin project was released. Talked in very strong terms about the importance of working in a holistic, caring way. A SWE in the audience spoke up, saying basically "look, we want to follow that approach, but it's hard, we have a lot of stakeholders to satisfy in order for a project to happen." Alexander was unyielding. "Once you've worked with love, you won't…
Re: Christopher Alexander has died
#96Re: Christopher Alexander has died
#97He had really interesting computational ideas about harmony. From The Nature of Order (2002) “As architects, builders, and artists, we are called upon constantly—every moment of the working day—to make judgments about relative harmony. We are constantly trying to make decisions about what is better and what is worse…” Following this, he published a paper on “harmony-seeking computation” as an approach to optimize “wh…
The 15 properties of life were, I believe, his attempt to find the universal rules underlying the design patterns he described in A Pattern Language. I've long thought that most of those properties could be described algorithmically and was curious what sort of system they would converge to. I suppose nature is one easy answer, but it's not a very useful one.
For those who are interested, there's a nice summary of the properties and analysis of how they relate to each other at http://web.sfc.keio.ac.jp/~iba/papers/PURPLSOC14_Properties.... and a more architecturally-focused take at https://www.archdaily.com/626429/unified-architectural-theor....
Re: Christopher Alexander has died
#98Re: Christopher Alexander has died
#99Massive PDF of A Pattern Language: https://arl.human.cornell.edu/linked%20docs/Alexander_A_Patt... But I recommend owning and reading it in print. Great book to dip in and out of at whim.
Re: Christopher Alexander has died
#100He had really interesting computational ideas about harmony. From The Nature of Order (2002) “As architects, builders, and artists, we are called upon constantly—every moment of the working day—to make judgments about relative harmony. We are constantly trying to make decisions about what is better and what is worse…” Following this, he published a paper on “harmony-seeking computation” as an approach to optimize “wh…