summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2023-08-19 11:16:08 +0300
committerPaul Buetow <paul@buetow.org>2023-08-19 11:16:08 +0300
commitf06bb0ee9f8dfc0a04f23c92983480047b6012bc (patch)
treede7670713dd27b559c40de0d193ff7f0a59b3440
parent5d9d54caaa282f773d0ceff9b362267bf76bce2c (diff)
cosmetic
-rw-r--r--gemfeed/2023-08-18-site-reliability-engineering-part-1.gmi.tpl2
-rw-r--r--gemfeed/DRAFT-site-reliability-engineering.gmi2
2 files changed, 2 insertions, 2 deletions
diff --git a/gemfeed/2023-08-18-site-reliability-engineering-part-1.gmi.tpl b/gemfeed/2023-08-18-site-reliability-engineering-part-1.gmi.tpl
index d31d3d28..d50ddec3 100644
--- a/gemfeed/2023-08-18-site-reliability-engineering-part-1.gmi.tpl
+++ b/gemfeed/2023-08-18-site-reliability-engineering-part-1.gmi.tpl
@@ -30,7 +30,7 @@ DC on fire:
## SRE and Organizational Culture: Navigating the Nexus
-At the heart of SRE lies the proactive mindset of 'prevention over cure'. Traditional IT models focused predominantly on reactive solutions, but SRE mandates a shift towards foresight. By adopting Service Level Indicators (SLIs) and Service Level Objectives (SLOs), teams are equipped with clear metrics and goals that guide them toward ensuring reliability and user satisfaction. However, these aren't mere numbers. They reflect an organisational culture prioritising user experience and constant system alignment with user needs.
+At the heart of SRE lies the proactive mindset of "prevention over cure". Traditional IT models focused predominantly on reactive solutions, but SRE mandates a shift towards foresight. By adopting Service Level Indicators (SLIs) and Service Level Objectives (SLOs), teams are equipped with clear metrics and goals that guide them toward ensuring reliability and user satisfaction. However, these aren't mere numbers. They reflect an organisational culture prioritising user experience and constant system alignment with user needs.
Another defining SRE concept is the "error budget". This ingenious framework accepts that no system is flawless. Failures are inevitable. However, instead of being punitive, the culture here is to accept, learn, and iterate. By providing teams with a "budget" for errors, organisations foster an environment where innovation is encouraged, and failures are viewed as learning opportunities.
diff --git a/gemfeed/DRAFT-site-reliability-engineering.gmi b/gemfeed/DRAFT-site-reliability-engineering.gmi
index f09faf54..cb0f398b 100644
--- a/gemfeed/DRAFT-site-reliability-engineering.gmi
+++ b/gemfeed/DRAFT-site-reliability-engineering.gmi
@@ -1,6 +1,6 @@
## On-Call Culture and the Human Aspect: Prioritising Well-being in the Realm of Reliability
-Site Reliability Engineering is synonymous with ensuring system reliability, but the human factor is an often-underestimated component of this discipline. It is evident that fostering a healthy on-call culture is as critical as any technical solution. In the world of constant alerts, pages, and incident management, the well-being of the engineers becomes paramount.
+Site Reliability Engineering is synonymous with ensuring system reliability, but the human factor is an often-underestimated component of this discipline. Fostering a healthy on-call culture is as critical as any technical solution. In the world of constant alerts, pages, and incident management, the well-being of the engineers becomes paramount.
Firstly, a healthy on-call rotation is about more than just managing and responding to incidents. It's about the entire ecosystem that supports this practice. Establishing happy and healthy on-call rotations is akin to possessing a superpower. This involves reducing pain points, offering mentorship, rapid iteration, and ensuring that engineers have the right tools and processes. It acknowledges that while systems are crucial, the engineers who maintain them are invaluable.