DevOps Patterns and Anti Patterns or DevOps Degradation and Lazy Developers

DevOps patterns and anti
patterns
or
DevOps Degradation and Lazy
Developers
Igor Goulko

• 200+ dives
• 25+ years IT experience (Ukraine (4), Israel
(13), Australia (10), USA)
• Rescue Diver, 6 PADI Certificates
• 3 Agile Certificates
• 2 Patents, implemented by IBM in Sametime
• Proud Dad twice and Happy Husband once
• Founder DevOps Talks Conference
igor.goulko@devopstalks.com

Horizons
The establishment of the automation department of General
Motors in 1947 forever transformed the industrial
manufacturing industry. The implementation of DevOps offers a
similar transformation for the future of an IT department.

History
• At the O’Reilly Velocity 09 conference, John Allspaw and Paul
Hammond give their now-famous talk entitled “10 Deploys a
Day: Dev and Ops Cooperation at Flickr.”
• October 2009: Patrick Debois organized the first DevOpsDays
- the first conference to an impressive collection of developers,
system administrators, toolsmiths, and others. After that the
twitter tag had been shorten to #DevOps. And the movement
has been known as DevOps ever since.

DevOps
• DevOps is the practice of operations and
development engineers participating
together in the entire service lifecycle, from
design through the development
process to production support.
• DevOps is also characterized by operations
staff making use many of the same
techniques as developers for their systems
work.

DevOps Myths
• DevOps is only for Startups
• DevOps replaces Agile
• DevOps is incompatible with ITIL
• DevOps is incompatible with information security and
compliance
• DevOps eliminates IT operations (NoOps)
• DevOps is just for “Infrastructure as Code” or Automation
• DevOps is only for open source software
*from “The DevOps Handbook”

You are not alone
• Transformation of Enterprise
• Start Up culture vs Enterprise power
• We are Agile enough. Why DevOps?
• Agile vs DevOps
• “We are not Google” and 200 lazy developers

“DevOps doesn’t work here” (c)

Culture
Culture is inherited from
❑Organizational chart/structure
❑People
❑Technologies and Tools

Teams
➢ On average, DevOps speeds development rate by 50%
➢ Team become the basis of competition. They build and operate the
highest value services and apps.
➢ Top performing DevOps teams choose their own tools
➢ Incedend budget management, incedent predictions and analyses.

All about people
„ ... Employees who are challenged, engaged, valued and rewarded
(emotionally, intelectually & financially) rarely leave, and more
importantly, they perform at very high level...” - Forbes

DevOps Jobs Market (USA)
DevOps Engineer ranks #2 on Glassdor’s 50 best jobs in US rankings!
➢Everage entry level salary for DevOps Engineer US$104, 508
➢ 57% of hiring managers are looking to fill DevOps engineer positions
➢ 60% of companies seeking source expertise are focused on DevOps
skills
➢ Over 160,000/day devops jobs gloablly for 2017
* Data from JFrog researches

DevOps Salaries [perm], Australia
• DevOps in Sydney AU$124,507
• DevOps in Melbourne AU$119,776
• DevOps in Brisbane AU$104,701
*from indeed.com
*IG: In reality +30%

DevOps Goals, Strategies and Mesuarments
“If the music industry were to try to make predictions about the
future like the software industry does, they would all be based on
details and trends in musical instrument manufacturing, with
almost no connection to songs, melody, or rhythm.”
John Allspaw

Are you sure that we can change culture?
• Structure and Organizational Charts as DevOps killers
• “Tell me what are tools we have to use to run DevOps”
• Coaching and technological leading
• Spread risks and wide range of technologies
• Legacy management, self-management and chaos
management

Transformation as Revolution

5 Steps to kill DevOps
1. Don’t touch organizational chart but change titles
2. Install all CI-CD tools and force engineers use it
3. Blame culture if something wrong
4. Create innovation management team
5. Educate “The ways we work” new hired engineers

Google Development
➢30,000 developers
➢60,000 commits per day
➢4M builds per day
➢500M tests per day
➢20,000 code reviews per day
*from Google Cloud presentation

Steps to initiate DevOps practice
1. Start from goals of transformation and innovation
2. Review and simplify organizational charts
3. Culture of transparency and blameless post-mortem
4. Innovations, spikes, labs and etc. Innovation committee
5. Continuous budgets reviews and analysis
6. Transformations as evolution has to be BAU

Technological chalenges
1. Infrastructure as code
2. Cloud migration
3. CI-CD
4. Containers or Serverless
5. Kubernetes
6. Deployments and Orchestration

Business, IT and Strategical Vision
1. Business vision, strategy, goals and ROI
2. IT goals
3. Product delivery
4. Business as product

John Willis Workshops, Melbourne and
Sydney
DevOps Workshops and DevSecOps Workshops

DevOps Workshops
• DevOps Patterns and
Practices
• High Performance
Organizations
• Vale Stream Mapping
• Maximize Flow
• Continuous Delivery
• Deployment Pipeline
• Managing Infrastructure
• Deployment Strategies
• Service Reliability
Engineering
• Understanding Monitoring
• Managing Complexity
• The Art of Learning
Organizations
• Blameless Culture
• Embracing Failure

DevSecOps Workshops
• Introduction to DevSecOps
• Why DevSecOps?
• Cyber Security in a DevOps
World
• Patterns and Practices
• DevSecOps Capability
Modelling
• Value Stream Mapping
(DevSecOps)
• Maximize Flow with Security
Resilience
• Security in the Software
Supply Chain
• Shift Left Security in the
Deployment Pipeline
• Securing Infrastructure
• Automated Testing for
Security
• Cyber Deployment Strategies
• Security Reliability
Engineering
• Understanding Security
Monitoring
• Managing Cyber Complexity
• Security and The Art of
Learning Organizations

DevOps Talks 2018 Sydney 27-28 August

Q & A

DevOps Patterns and Anti Patterns or DevOps Degradation and Lazy Developers

More Related Content

What's hot

Similar to DevOps Patterns and Anti Patterns or DevOps Degradation and Lazy Developers

Recently uploaded

DevOps Patterns and Anti Patterns or DevOps Degradation and Lazy Developers