Reposted by Simon Rohrer
𝗠𝗼𝗱𝗲𝗿𝗻 𝗘𝗻𝘁𝗲𝗿𝗽𝗿𝗶𝘀𝗲 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝗶𝗻𝗴 𝗳𝗼𝗿 𝗢𝘂𝘁𝗰𝗼𝗺𝗲𝘀 🏗️ Are traditional #EnterpriseArchitecture practices still fit for the modern enterprise? At #SAG2026, @simon.bvssh.com shows how modern EA can break dependencies and deliver better outcomes. 👉️ t1p.de/0y249
#SAGconf #DevOps
![Page with the quote in the post, as well as:
Ashby's Law: Address Variety with Variety Of course, our systems exist in complex contexts, with (generally) complex demands.
"In colloquial terms Ashby's Law has come to be understood as a simple proposition: if a system is to be able to deal successfully with the diversity of challenges that its environment produces, then it needs to have a repertoire of responses which is (at least) as nuanced as the problems thrown up by the environment. So a viable system is one that can handle the variability of its environment. Or, as Ashby put it, only variety can absorb variety." - John Naughton
Jabe Bloom: "The quickest way to explain Ashby's Law is as follows: If I am a fencer and I have 3 ways of thrusting at people, and everybody else has three ways of parrying those thrusts, it will be an even game. [.] I will be as in control as I can be. If someone else figures out another thrust, I will then be required to learn another parry otherwise I will always lose." Implication: The more different kinds of customers your business has, the more complexity you will need to absorb, in order to respond to that.](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:x6y4qbknc3mrsytkcs426i2q/bafkreifbwjbgxrobl4nila7foz4i7jnz42sk4457i72k2ctz55ygsq3y54)
