Ruth — of systems & design

@RuthMalan
3K Followers
2.9K Following
16.5K Posts

Software And Systems Architecture, more or less

Profile pic: drawing of me (gifted to me); upside down, as if in a reflection, with cloudy sky and little architecture drawing character hanging from frame

Webhttps://www.ruthmalan.com
Classeshttps://ti.to/bredemeyer/

Resilience Engineering “put doing things safely & effectively together to mitigate the risk of these kinds of viability crushing events[..] The starting point was the evidence that systems were more exposed to break down than stakeholders recognized, but major failures occurred less often only due to people who provided the extra adaptive capacity to make things go right.”

— David Woods

https://www.linkedin.com/posts/davidwoods3_a-key-driver-in-the-origin-of-resilience-share-7445158684449644544-oyKK

A key driver in the origin of Resilience Engineering RE was the need to help organizations outmaneuver complexities that arose in parallel with growth. Organizational struggles with complexity… | David Woods

A key driver in the origin of Resilience Engineering RE was the need to help organizations outmaneuver complexities that arose in parallel with growth. Organizational struggles with complexity undermined all aspects of system performance & threatened an organization's viability in terms of both large economic harm and safety harm (injuries and deaths). The runaway automation event that bankrupted the Knight Capital in 2010 was characterized by the same dynamics that occurred in events that led to substantial fatalities (eg Boeing crashes in 2018/2019). RE put doing things safely & effectively together to mitigate the risk of these kinds of viability crushing events (eg chapters in the 1st book). The starting point was the evidence that systems were more exposed to break down than stakeholders recognized, but major failures occurred less often only due to people who provided the extra adaptive capacity to make things go right. Doing things safely & effectively depended on supporting and not hindering this adaptive capacity. RE continues to learn from the ongoing stream of challenge cases usually well handled or nearly so. The knowledge, findings, technqiues that followed are even more important today as multiple destabilizing forces now combine to disrupt all systems at all scales up to societal. But need, capability, & adoption are different. Yes, adoption has been slow/spotty. The understanding of how adaptive systems function/malfunction has grown dramatically in conjunction with using this knowledge positively in many projects & sectors. Need is clearer & greater than ever. Now we must expand RE advances to function at/across community, regional, societal & even global scales. This is a tall order. Yet in times where the only certainty is high uncertainty ahead, investing in adaptive capacity is the best strategy available. Carney's Davos talk is a guide to adaptation & re-vitalization given the shock of "rupture" in geopolitical/economic sphere, and parallels what RE has learned about adaptation & re-vitalization for shocks in the safety/technology sphere. The irony is-all of us need to use what we have learned about adaptive capacity ourselves in our roles, including those of us who have tried to advance doing things safely and effectively. Carney highlights re-vitalization & reframing, despite the tensions, and cautions that retreat to the past or cautious incremental steps will be unable or insufficient to rise to the challenges of today.

LinkedIn
“This repository mirrors a publicly exposed Claude Code source snapshot that became accessible on March 31, 2026 through a source map exposure in the npm distribution. It is maintained for educational, defensive security research, and software supply-chain analysis.”
https://github.com/instructkr/claude-code
GitHub - instructkr/claude-code: Claude Code Snapshot for Research. All original source code is the property of Anthropic.

Claude Code Snapshot for Research. All original source code is the property of Anthropic. - instructkr/claude-code

GitHub

hm, I *loved* having pinned posts in a carousel on @Mastodon ...

(and I expect that few would "click to view all pinned posts")

Pear tree is trying, y’all!
Fighting my inner demons real hard ... I mean, I think wry snark about some of the "territorial" behavior in the "systems" field is "punching up" but sometimes punching is felt as just punching, especially when its about something we find useful...

“ADRs are short documents that capture a decision, structured into logs that reveal a history of architectural thinking for a product”

— Martin Fowler

https://www.linkedin.com/posts/martin-fowler-com_adrs-are-short-documents-that-capture-a-decision-share-7442232936789213184-oUSA

bliki: Architecture Decision Record | Martin Fowler | 61 comments

ADRs are short documents that capture a decision, structured into logs that reveal a history of architectural thinking for a product https://lnkd.in/e9K7VHDE | 61 comments on LinkedIn

LinkedIn
The post refers to Nygard’s 2011 “Document Architecture Decisions” post — which wasn’t the first to present a decision template (e.g., “Architecture Decisions: Demystifying Architecture,” by Jeff Tyree and Art Ackerman was published in IEEE Software in 2005), but it was the post that really had impact.

“ADRs contain not just the decision, but also a brief rationale for the decision. This should summarize the problem that led to this decision being needed and the trade-offs that were taken into account. A good way to think of them follows the notion of “forces” when writing a pattern.”

https://martinfowler.com/bliki/ArchitectureDecisionRecord.html

bliki: Architecture Decision Record

A short document that captures a single decision, structured into a log to provide a history

martinfowler.com

“A general rule is to follow an “inverted pyramid” style of writing, commonly associated with news stories. The key is to put the most important material at the start, and push details to later in the record.”

https://toot.thoughtworks.com/@mfowler/116284886338044351

Martin Fowler (@[email protected])

NEW POST ADRs are short documents that capture a decision, structured into logs that reveal a history of architectural thinking for a product https://martinfowler.com/bliki/ArchitectureDecisionRecord.html

Thoughtworks’ Mastodon instance