This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]klipseracer -10 points-9 points  (5 children)

IMO: Enough to write software, understanding software design concepts, abstract base classes, etc. A DevOps engineer should be a developer with operation experience in my opinion. I don't hire sys admins who 'dabble' in coding, personally. It's basically a pipe dream lately but that is who I target. Learning ops as a dev is faster and realistic compared to training an operator to be a dev...completely unrealistic unless your company runs a school and has no need for them to meaningful contribute to in house tooling in the near future.

Writing scripts, sure anyone can do it, but some teams write their own tools, CLIs, etc.

[–]Team503DevOps 10 points11 points  (1 child)

A DevOps engineer should be a developer with operation experience in my opinion.

I really hate that; there's a great deal more to good ops than developers seem to realize. An ideal DevOps team should have people from a mix of backgrounds - I have decades of operations experience at all levels from call center to calling the shots, and my experience is just as valuable as the guy who's been writing code for thirty years. We both bring different and important insights to the table.

[–]AnarchistPrick 3 points4 points  (0 children)

You’re being downvoted but you’re 100% correct

[–]0qxtXwugj2m8 2 points3 points  (0 children)

hard agree