10 bad habits DevOps admins must break

WWT's Matthew Perry comments on mistakes DevOps admins can make in their implementation journey.

March 27, 2018 2 minute read

Posted by Tech Republic on March 22, 2018:

As DevOps is gaining traction in many organizations, including Adobe, Amazon, and Target, DevOps administrators must work to integrate development, operations, support, and management for better productivity and a smoother overall workflow.

Lucrative careers in the field are growing rapidly: DevOps engineers came in no. 2 on Glassdoor's list of best tech jobs in America for 2018.

"Generally, companies have at least a cursory understanding of what DevOps is," Justin Rodenbostel, vice president of open source application development at SPR. "That said, many of these same organizations are still struggling with finding the right path to adoption, understanding how to start to adopt and understanding whether they have capabilities mature enough to get started and be successful."

Many companies are still trying to figure out what DevOps means within small pockets of their organization, said Matthew Perry, director of IT operations for WWT Application Services group. "They have early adopters using DevOps methodologies as they continue to look for patterns that they can apply throughout their organization," he added.

Here are 10 mistakes for DevOps admins to avoid in their implementation journey.

1. Fearing failure

DevOps admins must avoid thinking their environment is perfect, said Jim Halpin, team lead of LaSalle Network's technology recruiting practice. "Be willing to fail," Halpin said. "Sometimes you will make decisions or implement a tool that is not the best choice for the environment. Failures can lead to innovation."

While developers may want to see the fruits of their labor, that's not always the case, said IBM distinguished engineer Michael Elder. "Adopt an NCIS (No Code Is Sacred) experiment-driven practice that insists on self-editing and accepts the 'don't be afraid to fail' mentality," Elder said. "This will allow teams to form questions, quickly implement a means to gather data and try alternatives, and then use real user behavior and feedback to make a final decision."

View the full article.

Read full article here
Share this