That doesn’t mean that you are just rolling the dice on
crackpot ideas; rather, it means having a dynamic and
disciplined approach to experimentation and risk taking.
It’s very rare that success happens on the first try. When
problems occur, avoid pointing fingers and blaming
people; instead, figure out what went wrong and what
could be improved to make it better. Figure 13-19 shows
the third way of DevOps, which focuses on continuous
experimentation and learning.
Figure 13-19 Third Way: Continuous
Experimentation and Learning
DevOps talks a lot about continuous improvement and
fixing issues to make the system perform better. It’s a
noble goal, but when do you find time? The simple
answer is that you need to make time. In other words,
you schedule time to get people focused on improving
the system and try new methods and technologies.
Finally, you must build a culture of sharing and learning.
A simple method to accomplish this is to create shared
code repositories and get those treasure troves of
information off individual laptops and available to the
rest of the organization.
The following are the key characteristics of the third way:
Conduct dynamic, disciplined experimentation and risk taking
Define time to fix issues and make the system better
When things go wrong, don’t point fingers