diff options
| author | Paul Buetow <paul@buetow.org> | 2024-09-07 16:45:26 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2024-09-07 16:45:26 +0300 |
| commit | 8966f9e2336758073fc48f147dbf691d5902aabd (patch) | |
| tree | cf1881eaa59e0b7204c4ad31ee50bb1b0307fa32 /gemfeed/2024-09-07-site-reliability-engineering-part-4.gmi | |
| parent | 362bdf8036bc9c7e7c4470bdb8a870cd67690f26 (diff) | |
Update content for gemtext
Diffstat (limited to 'gemfeed/2024-09-07-site-reliability-engineering-part-4.gmi')
| -rw-r--r-- | gemfeed/2024-09-07-site-reliability-engineering-part-4.gmi | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/gemfeed/2024-09-07-site-reliability-engineering-part-4.gmi b/gemfeed/2024-09-07-site-reliability-engineering-part-4.gmi index 56105315..4500e7bb 100644 --- a/gemfeed/2024-09-07-site-reliability-engineering-part-4.gmi +++ b/gemfeed/2024-09-07-site-reliability-engineering-part-4.gmi @@ -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 |