DOES17

your experience is amazing, we look forward to leveraging it in a more efficient manner that will benefit both you and the company.

I think ops guys/gals have great oppty bc ops will evolve to multicloud which is just another datacenter like thing

. @JerDoug i don't have enough space. I'll say that your investment in your discipline is more than performing tasks. You provide invaluable operational guidance.

All automation will destroy some jobs, create and change others. The best place to be is on the crest of that wave (not underneath it).

@DOES_USA See my earlier tweet about leaders making themselves obsolete... don't be afraid of progress! Niches and opportunities are created, there!

I'd say it's 2017... are people still afraid of automation or is this just a strawman thrown out to cover for some other fear?

Embrace change and the opportunity to learn new things. If it can be automated, it should be.

This is a huge issue in the netops world. I try to gently say that automation is the new normal and not automating is an avenue to unemployment...

btw: gr8 question. To me it's like the mainframe guys. Some hung around til the end many figured out the new way and jumped over to the new wave called Mini's and LANs and PCs

OH: "70% of ops engrs didn't join our effort & team suffered b/c of it. We really needed their expertise."

embrace the change lest it leave you behind. DevOps is not the opposite of ITIL, they are closely intertwined

@furrier correct. just as server administrators became virtualization administrators. Many are transitioning again. evolution doesn't stop.

Most people I've talked to have been super excited about automating away the boring stuff and being able to leverage their with for cool (and useful!) stuff

to me devs will always be devs but ops guys will still be in charge

Move up the value stream. If you are firefighting start working proactively on how to make your job redundant before release - that's your new job

Every role has elements that will become mainstream, mundane, repeatable and automatable. Identifying new areas that do not have these characteristics where to head. E.g. moving to cloud still needs people :)

Technology is for automation. People are for solving problems. Let tech do the boring, repetitive stuff. Embrace the exciting, challenging work. Let yourself be promoted.

@kaimarkaru I like the positive tone ... will be using this ... thx! :)

OH last week: "many MS automation holdouts were the old Microsoft Small Business Service admins"

@nicolefv Nicole you got this :-)

.@RealGeneKim Did I get that right? We had it at Tripwire: Exchange, IIS/ASP, what else was in there?

@petereeles and instead of "with" there should be "wit" (I have a built-in auto-correct in my brain)

.@RealGeneKim @jsnover Your characterization of this archetype was a huge aha moment for me. @yesthattom

that it just about Dev and Ops, you have to bring everyone with you.

That it is scary...

that you can "do" DevOps. You "do" continuous delivery as part of a DevOps culture.

( should say "do" CD and other stuff probably... )

That DevOps is the "Wild West" with out-of-control developers. It's in fact the complete opposite if done correctly.

That DevOps is an IT problem

@kmugrage agree - there are DevOps practices and a cultural mindset that an organization needs to have

That's it's all about cloud and technology

that's it's all about automation

That Ops people don't want to 'do' DevOps

There's one exact place to start/do. "Where should I start?" It depends. Tell me where you are now, then I can tell you what to do next to optimize your transformation and outcomes.

that DevOps is somebody else's job

@nicolefv yes!! The starting line moves faster than the target

"Start where you are" :) rather than from where you want others to think you are

that it is not possible !!! it is possible but if differs per organization there is no one size fits all

That when the IT function can do things quicker and with less risk the business would be grateful and would welcome small frequent changes

@kaimarkaru Yes. People confuse "can't see how to do" with "don't want to do".

@damonedwards Takes us back to lack of respect. Kind of expecting the worst from people - sometimes (but not always) because one would behave like that themselves.

Curling. Definitely curling.

heptathlon: multi disciplinary FTW :)

underwater basket weaving

@DOES_USA Quidditch?

Hurdles, and managing to overcome them :)

DevOps is much more important than any sport (like cricket)

Hockey (Played well) - speed, fast flowing, teamwork and passing to achieve a goal for your team - avoid getting pinned in a corner and getting pummeled

I would say Triathlon. Ironman in particular. Multidisciplinary and a long distance activity. And I am a huge fan of both!

@Josh_Atwell 1 ounce? or 2-ounce curls?? ("make mine a double!")

Rephrasing @carmendeardo: "DevOps is like hockey; you get stuck in corner and then pummeled" Haha

How about just getting people on a team to play the same sport?

@carmendeardo Rangers Bruins would have been the dream series re: hockey

@damonedwards @DOES_USA Yes! Sportsball is good when your whole team is sportsing together!

Soccer as opposed to American Football as you need Offense and Defence on the field at the same time

@RealGeneKim Devops: Pass Shoot Score !

Lacrosse

Something like sailing or bobsled / bobsleigh - it requires a team working together and there are no "hero goal-scorers".

from a mud race, 100 m sprint, triathlon, Tour de France, rally driving to Formule 1

USA women's soccer. something for everyone and drives revenue. (okay, except pretend we compensate the players appropriately.)