"What you'll need to succeed"

[Baron von Lotsov]

Looks like bullshit baffling brains to me:-



DevOps (development and operations) is an enterprise software development phrase used to mean a type of agile relationship between development and IT operations. The goal of DevOps is to change and improve the relationship by advocating better communication and collaboration between these two business units.

Exactly, and of course the one thing it clearly does not do is improve communications, or we would know what the hell it was.

[papasmurf]

Looks like bullshit baffling brains to me:-



DevOps (development and operations) is an enterprise software development phrase used to mean a type of agile relationship between development and IT operations. The goal of DevOps is to change and improve the relationship by advocating better communication and collaboration between these two business units.

[Baron von Lotsov]

It's a job right!

You will also possess the following:



 Extensive experience and thorough understanding of DevOps

https://www.totaljobs.com/job/principal-software-engineer/hays-job88778770">https://www.totaljobs.com/job/principal ... ob88778770">https://www.totaljobs.com/job/principal-software-engineer/hays-job88778770



The trouble is that even Wikipedia does not understand what DevOps actually means.

DevOps is a set of practices that combines software development (Dev) and information-technology operations (Ops) which aims to shorten the systems development life cycle and provide continuous delivery with high software quality.[1][2]

Wow!!!

Academics and practitioners have not developed a unique definition for the term "DevOps."

OK so we have a bunch of published references on that statement.



Then we check the talk section

This article is a joke, right from the very first poorly written paragraph. DevOps is culture, period.

I'm surprised this article does not have a "Critical" section, common to most other technology-related articles. I've heard anecdotal arguments that DevOps dilutes the specific skills of many engineers and teams, for example, and its implementation without defining responsibilities can cause organizational friction and lower productivity.

This does not make sense and needs to be reviewed with a close reading of the source. A change in thinking is cultural change.



The article is in IT management speak, and needs to define terms to meet the needs of the general wikipedia audience.

https://en.wikipedia.org/wiki/Talk:DevOps">https://en.wikipedia.org/wiki/Talk:DevOps





And the talk goes on and on and on, and one thing you can say for certain is the world's experts do not know what the hell it is, because every dude has a different idea what it is.



So you have to put on your suit and lie like mad and tell them that you are the world's greatest practitioner of this sht.