this post was submitted on 10 Jun 2023
15 points (94.1% liked)

Programming

17313 readers
311 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 [email protected]

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
15
Devs don’t want to do ops (www.infoworld.com)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
9 comments fedilink hide all child comments
 

TLDR provided by ChatGPT:

As software development grows more complex, the devops approach, which merges software development and IT operations roles, is under scrutiny. Although devops has sped up updates and tightened feedback loops, it's often overburdening individuals by blurring developer and operator roles. Developers have voiced reluctance to handle operations, citing the specialized skills needed. The potential solutions include realigning responsibilities to empower developers with timely information, using container orchestration technologies like Kubernetes to separate developer and operator concerns, and expanding the roles of Site Reliability Engineering (SRE) and platform engineering. The future of software development may require a blend of devops, SRE, and platform engineering to effectively address the growing complexity.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 1 year ago

My target environment is small and specific enough. I value having control and opportunity greatly. I would hate to have barriers to deployment, analysis, changes.

If it exceeds the complexity or workload of where it makes sense, it probably makes more sense as a team collaboration rather than separating devs from ops "again".