diff options
| -rw-r--r-- | gemfeed/2023-08-20-site-reliability-engineering-part-3.md | 2 | ||||
| -rw-r--r-- | index.md | 2 | ||||
| -rw-r--r-- | uptime-stats.md | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/gemfeed/2023-08-20-site-reliability-engineering-part-3.md b/gemfeed/2023-08-20-site-reliability-engineering-part-3.md index 534502da..6bcc0be8 100644 --- a/gemfeed/2023-08-20-site-reliability-engineering-part-3.md +++ b/gemfeed/2023-08-20-site-reliability-engineering-part-3.md @@ -38,7 +38,7 @@ This is the third part of my Site Reliability Engineering (SRE) series. I am cur Site Reliability Engineering is synonymous with ensuring system reliability, but the human factor is an often-underestimated part of this discipline. Ensuring a healthy on-call culture is as critical as any technical solution. The well-being of the engineers is an important factor. -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. This involves reducing pain points, offering mentorship, rapid iteration, and ensuring that engineers have the right tools and processes. One ceavat is, that engineers should be willing to learn. Especially in on-call rotation mixing SREs with other engineers (for example Software Engineers or QA engineers), it's difficult to motivate everyone to engage. QA engineers want to test the software, Software Engineers want to implement new features; they don't want to troubleshoot and debug production incidents. It can be depressing for the mentoring SRE. +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. This involves reducing pain points, offering mentorship, rapid iteration, and ensuring that engineers have the right tools and processes. One ceavat is, that engineers should be willing to learn. Especially in on-call rotation mixing SREs with other engineers (for example Software Engineers or QA Engineers), it's difficult to motivate everyone to engage. QA Engineers want to test the software, Software Engineers want to implement new features; they don't want to troubleshoot and debug production incidents. It can be depressing for the mentoring SRE. Furthermore, the metrics that measure the success of an on-call experience are only sometimes straightforward. While one might assume that fewer pages translate to better on-call expertise (which is true to a certain degree, as who wants to receive a page out of office hours?), it's not always the volume of pages that matters most. Trust, ownership, accountability, and effective communication play the important roles. @@ -1,6 +1,6 @@ # foo.zone -> This site was generated at 2023-08-20T12:35:50+03:00 by `Gemtexter` +> This site was generated at 2023-08-20T12:41:13+03:00 by `Gemtexter` ``` |\---/| diff --git a/uptime-stats.md b/uptime-stats.md index 55a21c37..162bf1a1 100644 --- a/uptime-stats.md +++ b/uptime-stats.md @@ -1,6 +1,6 @@ # My machine uptime stats -> This site was last updated at 2023-08-20T12:35:50+03:00 +> This site was last updated at 2023-08-20T12:41:13+03:00 The following stats were collected via `uptimed` on all of my personal computers over many years and the output was generated by `guprecords`, the global uptime records stats analyser of mine. |