this post was submitted on 15 Jul 2023
49 points (98.0% liked)
Asklemmy
43842 readers
612 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My efforts reduce time spent in incidents for on call engineers. I actively allow them to work less, and they usually fight me on it, hahaha.
I'm an automation engineer working for a large cloud operator.
I'm a software engineer on a team that is known around the org to have the worst on-call load out of anyone else. You are definitely underappreciated if your work saves them lots of time!
Keep fighting the good fight. In my experience with SRE/automation work, people tend to fight change just because it's change and not realize just how much time they're spending on toil and similar tasks.
Oh there's lots of buy in from the top. We can't continue to scale without automation.
It's either happening with the current operators, or without them. :)