ishenwei/nexus
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sreweekly: 528 期数据 + 全文抓取（articles/pages + markdown 正文扩充）

Browse Source
This commit is contained in:
weishen
2026-09-10 20:52:28 +08:00
parent f715edd2ef
commit 6f956f9c08
100 changed files with 38563 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
sreweekly/markdown/529/08-traditional-versus-resilience-engineering-views.md
View File

@@ -9,3 +9,29 @@
> I thought it would be a useful exercise to brainstorm some of the differences in focus between what I’ll call the traditional view of reliability, and the resilience engineering view.
It’s short (just a table), but it definitely made me think.
## 正文
As a fan of resilience engineering, I often differ with people on where we should focus our scarce engineering cycles in order to improve reliability.
I thought it would be a useful exercise to brainstorm some of the differences in focus between what I’ll call the *traditional* view of reliability, and the resilience engineering view.
| **Traditional view focuses on** | **Resilience engineering view focuses on** |
| accountability | coordination |
| prioritization | goal conflicts |
| risk mitigation | risk trade-offs |
| better processes and conformance thereof | more expertise |
| quantitative | qualitative |
| root cause | interaction of multiple factors |
| action items | insight |
| preventing future incidents, ensuring all incidents are novel | better handling of novel incidents |
| reducing complexity | navigating complexity |
| objectives | production pressure |
| robustness | resilience |
| human variability as liability | human variability as asset |
| building accurate system model | repairing inevitable model errors |
| rigor | improvisation |
| explicit knowledge | tacit knowledge |
| automation, benefits of | automation, risks introduced by |
## One thought on “Traditional versus resilience engineering views”