this post was submitted on 05 Jan 2026
332 points (99.4% liked)
PC Gaming
13145 readers
825 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You'd be surprised. DevOps are, at least by my experience, SEVERELY overworked and understaffed. Even such things as writing a script is not always so easy, especially when security credentials are involved. Depending on the company there may be many layers of red tape for using security credentials stored in a secrets vault, so sometimes such things aren't even possible since there is no official work request for that automation.
A lot what you mention is for sure true. My problem usually is deferring infra work to people that should not do it. More often than not I see so called "devops teams", and once I see the elements on those, is very clear people that are actually for infra are either insufficient, missing, or straight up not enough permissions to do stuff. Yo would be shocked how many times I hear managers say " ah well, I bet one ofb our developers knows how to do infra work"