The Devops Handbook 读书笔记05 Chapter3

Chapter3 The Second Way: The Principles of Feedback

第二种方法描述了在价值流的所有阶段实现从右到左的交互快速和持续反馈的原则。我们的目标是创造一个更安全、更有弹性的工作体系。
我们并不希望发生重大故障的时候才发现问题。因此，我们通过创造快速、频繁、高质量的信息流贯穿于我们的价值流和我们的组织，包括反馈和前馈循环。这使我们能够在问题更小、更便宜、更容易解决的时候发现和纠正问题;避免问题在他们造成灾难之前才被发现;并创造组织学习融入未来的工作。当故障和事故发生时，我们把它们当作学习的机会，而不是惩罚和责备的原因。

创建快速反馈对于在技术价值流中实现质量、可靠性和安全性至关重要。
我们通过观察问题的发生，聚集并解决问题来建立新的知识，将质量推向源头，并不断优化下游工作中心。

We make our system of work safer by creating fast, frequent, high quality
information flow throughout our value stream and our organization, which
includes feedback and feedforward loops. This allows us to detect and remediate
problems while they are smaller, cheaper, and easier to fix; avert problems
before they cause catastrophe; and create organizational learning that we
integrate into future work. When failures and accidents occur, we treat them as
opportunities for learning, as opposed to a cause for punishment and blame.

如何在复杂的系统中安全工作

WORKING SAFELY WITHIN COMPLEX SYSTEMS

复杂的系统有两大特征：
1、一个过于复杂的系统，无人可以做到对它了如指掌，组件与组件之间难以分离
2、在复杂的系统中做重复的事情，不一定可以带来可预测的结果，即不一定百分百就没问题。

在复杂的系统中，遇到问题是不可避免的，所以我们必须设计一个安全的系统，让我们可以毫无顾虑的去执行工作，有信心任何错误都能尽早被检出，在造成灾难性后果之前被检出，如工人受伤，产品缺陷，或对顾客的负面影响。

有何方案？直接引用书里的话吧！
**我的理解就是：**加强设计和操作过程中的管理、在组织中贯穿学习新知识和总结问题的文化、裂变出新的领导发挥作用。

we can make it safer to work in complex systems when the four following conditions are met：
1.Complex work is managed so that problems in design and operations are revealed
2.Problems are swarmed and solved, resulting in quick construction of new knowledge
3.New local knowledge is exploited globally throughout the organization
4.Leaders create other leaders who continually grow these types of capabilities

监控问题的发生

SEE PROBLEMS AS THEY OCCUR
我们通过在工作系统中创建反馈和前馈循环来实现这一点。每一步操作都应该有检测和监控。
在这里瀑布型项目就是妥妥的反面教材，即花1年或者半年开发完之后，再交给测试来测试。

our goal is to create fast feedback and fastforward loops wherever
work is performed, at all stages of the technology value stream, encompassing
Product Management, Development, QA, Infosec, and Operations. This includes
the creation of automated build, integration, and test processes, so that we can
immediately detect when a change has been introduced that takes us out of a
correctly functioning and deployable state.

说起来，自动化测试和pipeline真的很有用哦。
BTW，测试只是一种反馈。

聚集并解决问题

SWARM AND SOLVE PROBLEMS TO BUILD NEW KNOWLEDGE
当问题发生时，拉响警报，动员所有可能解决这个问题的人，一起解决这个问题。如果这个问题不解决，有可能需要停止接下来的工作流，以免扩大范围。

It prevents the problem from progressing downstream, where the cost and
effort to repair it increases exponentially and technical debt is allowed to
accumulate.
It prevents the work center from starting new work, which will likely
introduce new errors into the system.
If the problem is not addressed, the work center could potentially have the
same problem in the next operation (e.g., fifty-five seconds later), requiring
more fixes and work.

优化下游的工作中心

ENABLE OPTIMIZING FOR DOWNSTREAM WORK CENTERS
根据精益原则，我们最重要的客户其实是我们的下游，我们需要优化我们的工作，以至于帮助他们更好地解决问题。
为此，我们需要从源头上控制质量，并对一切可操作的非功能需求进行设计，例如，“体系结构、性能、稳定性、可测试性、可配置性和安全性”，与用户特性一样，这些非功能需求都需要优先考虑。

According to Lean, our most important customer is our next step downstream.
Optimizing our work for them requires that we have empathy for their problems
in order to better identify the design problems that prevent fast and smooth flow.