I'm a big fan of DevOps; for one reason or another, I've been in this 'space,' if you will long before it was DevOps...since about 2004/2005. If you ask me what DevOps is, this is the answer that I will always give:
It empowers the developers and developer teams to get up to speed quickly when writing new software, or when they add new team members to their teams,
It streamlines and optimizes the delivery of software within the service lifecycle, and
It changes and improves the relationships between development teams and IT operations by advocating better communication and collaboration between the two business units.
When done correctly, DevOps can help developers write better code, push to production faster, and be agile in their iterations and respond to the needs of both external as well as internal customers quicker.
> If you ask me what DevOps is, this is the answer that I will always give.
Nothing in your answer says what it is. It just tells things that doing/using it will allegedly accomplish/enable. Is anything that accomplishes all of those things considered to be "DevOps"?
Great, and I still have no idea what I'll actually be doing day to day. If I didn't know anything about it id think you were just trying to pretty up a pig of a job.
It empowers the developers and developer teams to get up to speed quickly when writing new software, or when they add new team members to their teams, It streamlines and optimizes the delivery of software within the service lifecycle, and It changes and improves the relationships between development teams and IT operations by advocating better communication and collaboration between the two business units.
When done correctly, DevOps can help developers write better code, push to production faster, and be agile in their iterations and respond to the needs of both external as well as internal customers quicker.