A lot of thought today is linear when it should be more encompassing of reality. The minimalist breakdown of essential parts is a logical one, but only because we have to determine just what correlates to what and in what manner. Causation has been a hard thing to prove in its own right.
Through this course, I’ve seen that it’s important to see the world (and the smaller, [possibly] more contained systems within it) as always affected by some means by something else. It’s a little on the side of Chaos Theory, but as with everything else, we put our own (perhaps somewhat arbitrary) limits on the system and its effects.
And, arguably, it’s that arbitrary aspect in addition to the inability to assuredly pinpoint causality (in some cases) that makes systems thinking really interesting.
As with everything else with architecture (though systems are certainly not contained only to architecture), not everything has a clear answer. It, and life, seems to be about finding solutions as we go.
Through the Bay Game earlier this semester, we’ve seen how simple moves can disrupt, improve, or cause an equilibrium in the Chesapeake Bay’s health.
A single plan implemented over a twenty year period (the length of our Bay Game), is not necessarily the answer. Twenty revised plans as time progresses, adapting to issues regarding the bay’s health might come closer. It also might not – given that a plan a year might not take into consideration the resilience of the system that had been in play the year before, acting too quickly to change things that might resolve themselves.
Finding answers, right and wrong, will be an experience that takes careful consideration, and I look forward to it each step of the way.