summaryrefslogtreecommitdiff
path: root/gemfeed
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2024-09-07 16:45:25 +0300
committerPaul Buetow <paul@buetow.org>2024-09-07 16:45:25 +0300
commit46c8b42b07141d59994997e1370d90d4065769dd (patch)
tree497e304922598efe2ff3083aaa8fa9fbe7d58cec /gemfeed
parenta2297d659620c860ca44eaa324a9a601f23977e6 (diff)
Update content for md
Diffstat (limited to 'gemfeed')
-rw-r--r--gemfeed/2024-09-07-site-reliability-engineering-part-4.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/gemfeed/2024-09-07-site-reliability-engineering-part-4.md b/gemfeed/2024-09-07-site-reliability-engineering-part-4.md
index 3425956a..4af52caf 100644
--- a/gemfeed/2024-09-07-site-reliability-engineering-part-4.md
+++ b/gemfeed/2024-09-07-site-reliability-engineering-part-4.md
@@ -67,3 +67,5 @@ It is important that runbooks are not a "project to be finished"; runbooks have
By structuring the onboarding process with KT sessions, shadowing, comprehensive runbooks, and a feedback loop, we've been able to fast-track the process from six months to just six weeks. This not only prepares our engineers for the on-call rotation quicker but also ensures they're confident and capable when handling incidents.
If you're looking to optimize your on-call onboarding process, these strategies could be your ticket to a more efficient and effective transition. Happy on-calling!
+
+[Back to the main site](../)