this post was submitted on 15 Oct 2024
322 points (99.4% liked)
Programming
17398 readers
156 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'd wager not being given time to tackle technical debt is indeed frustating...
I keep seeing a pattern of sre/devops/sysadmin tasks being given back to developers and canning the SREs. Hard to understand why. Then some of the SWE get stuck basically focussing on infra SRE stuff and become unwilling SRE more or less. Circle of life? Do the old devops folks get made into glue or something?
"Devops" original intent meant you don't have a separate "operations" department separate from teams "developing" your product / software due to competing incentives. "Dev" wants to push new stuff out faster; "ops" wants to keep things stable. Or "dev" needs more resources; but "ops" blocks or doesn't scale the same. The idea was to combine both "dev" and "ops" people onto projects to balance these incentives.
Then managers and cloud clowns repurposed it to apply to every person in a project so now every member is expected to perform both roles (badly). Or even more overloaded to somehow refer to "developer infrastructure" teams.