You don’t have an Agile Engineer, so why do you have DevOps Engineers? Are they supposed to engineer the DevOp?

Why is it that your DevOps engineers look like a less angry systems administrator? Is Jenkins really that awesome? Has Docker sprinkled Unicorn droppings on the infrastructure?

You’ve had DevOps Engineers for a couple years now, but the number and complexity of problems is still increasing. Is DevOps just a scam?

Start with a simple comparison: Developers solve problems by writing many lines of code. Ops solve problems by reading about settings for hours and making a single change. What are the other personalities required to make successful systems? These personalities belong on the same project at the same time, not in some sequence that absolves previous steps from downstream responsibility.

What does DevOps really look like in a successful software organization?


Comments are closed.

Darren Wright at 10:25 on 20 Apr 2018

Good talk.

Eric Poe at 10:49 on 20 Apr 2018

Very energetic & stentorian speaker. I loved that the slides were driven by the script, not the script driven by the slides.

A suggestion for usability, though: please don't use dark text on a darker background when presenting via projector. This makes it difficult to read unless the projector is super bright.

Paul Dejean at 13:49 on 20 Apr 2018

I liked that you lobbed the books rather than pitching them so no one got hit in the face.

John Vernier at 15:24 on 20 Apr 2018

Great talk! Also, thanks for the copy of "The Phoenix Project"! Sitting up front because I'm half deaf pays off sometimes :)

Philip at 09:26 on 21 Apr 2018

Inspiring, to the point.

Daniel Kadosh at 14:08 on 21 Apr 2018

Energetic talker, very engaging, a great wisdom to share.

Excellent talk. The energy exuded from the speaker kept the audience, including myself, engaged. Who doesn't like free books being tossed at them? Heh

Ed Barnard at 19:17 on 22 Apr 2018

Good information from the perspective of "been there done that", DevOps explaining the way it is to Software Engineering. Handing out stacks of books as follow-up was brilliant and appreciated (have mine next to me).

ALL talks on a dark background with that particular projector were unreadable including Boyd's. In general I have trouble with low-contrast colors such as grey on black, blue on blue, etc. Fortunately the talk did NOT depend on the text on the slide. The talk was compelling on its own.

The talk was a little weird getting started—could have just been me but the first 5-10 minutes seemed to be rough in getting to the main premise. However, the premise itself was good and I couldn't agree more with the content. Ultimately, you should let your values dictate what you do and why.

Great talk!