21–23 of 23 posts
40 years ago IBM called these guys "systems programmers". That this is a new concept to some people is symptomatic of a wider problem in the industry: everything needs to be shiny and new so every 10 years we reinvent the wheel with new jargon.
Linky - http://www.jedi.be/blog/2010/02/12/what-is-this-devops-thing... Call it what you will, 'DevOps' is just what you'd expect a good sysadmin to do in a sufficiently large org. That there is on going friction between developers and sysadmin ("it works on my box" is a valid excuse?) is perhaps a larger sign of the culture and people involved.
In a 100% ideal scenario an organization would only need developers as every possible failure/problem would be covered and handled by automation. Obviously the real world is different. New code is deployed that has bugs, there are unpredicted events, there are complex failure scenarios that are difficult to automate etc. A DevOps engineer may write automation software in conjunction with developers to automate the op…
40 years ago IBM called these guys "systems programmers". That this is a new concept to some people is symptomatic of a wider problem in the industry: everything needs to be shiny and new so every 10 years we reinvent the wheel with new jargon.
DevOps is not just "writing automation tools". If that's all you're getting out of this, you're missing 90% of what's going on.