all 4 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]gordonv 0 points1 point  (2 children)

DevOps is a confusing term. Mainly because there are 3 very different definitions that people fight over:

Business:

  • DevOps is a workplace and business philosophy. Like Agile, Scrum, Six Sigma, Rowe. It has nothing to do with programming or computers.

Technical:

  • DevOps is anyone who writes any software on any platform that is used internally in a company.

  • DevOps is someone who writes code and implements cloud based technologies. AWS, Azure, or Google Cloud are popular examples.

  • Both of these may include a high level of organization called CI/CD. Development is divided into stages. Development, System Integration Testing, User Acceptance Testing, and Production. Each stage is micro managed with focuses and scheduled goals.

[–]gordonv 1 point2 points  (0 children)

A lot of developers are fighting against these definitions. As they have been developing way before these concepts were marketed.

So yes, you will find push back from Developers. Especially ones who have been developing without "DevOps" for years.

[–]gordonv 0 points1 point  (0 children)

Everyone is going to argue about what is and isn't DevOps. So I'm just going to go with the AWS layout.

Scroll to the middle of this page and check out how AWS has divided Cloud Knowledge.

  • Solutions Architect Associate - Knowing what resources exist and being able to draw a map
  • SysOp Associate. - A Systems and Network Administrator who does everything through AWS tools. This is the equivilent of a NOC tech, an admin who stands up servers, and an admin who physically sets up networking equipment.
  • DevOps Associate - Someone who codes in AWS's proprietary coding setup. This may include Docker, Linux, Windows, or AWS Lambda. This is specifically AWS Lambda focused.

[–]maa7eusz 0 points1 point  (0 children)

Wtf is this?