Alexios07 said:
Sounds like you got it from a wiki article. It depends on the company you work for, most of the time, DevOps is an actual position. It can be a Sysadmin who can code and script, or an experienced Dev who knows how to Sys Ad.
I've never actually heard anyone use "DevOps" as a method to do something. Usually they go with some buzzwords like agile, kaban, cloud or synergy etc.
DevOps is so much more that scripts automation and coding... you're thinking about developing on cloud (PaaS)... which is DevOps for small firms, but think of big legacy enterprises where you have two distinct and often competing groups one who develop and maintain the application and another who operate the infrastructure.
It's about bringing development and operations together to work more effectively. Traditionally these two groups don't play well with other as developers wish to quickly promote their code throu the lifecycle and operations require inuneroua acceptance sign off to make sure the production environment won't break!
Traditionally ITIL processes were implemented to ensure proper operations, stability and governance; as a result developers had to jump through many to get their application fix finally deployed for the end user... change management processes used to have weekly or monthly approval committees breaking the DevOps cycle altogether... and that's just one of the many examples...
On the whole to a new kid who was born on the cloud era and is used to AWS, DevOps (continuos deployment) may be natural and the only thing he's ever known... but for people who have been out there for a while DevOps is about changing a company's culture.
And yes... this is straight out of Wikipedia