Operations Anti-Patterns, DevOps Solutions shows how to implement DevOps techniques in the kind of imperfect environments most developers work in. Part technology tutorial, part reference manual, and part psychology handbook, this practical guide shows you realistic ways to bring DevOps to your team when you don't have the …
Operations Anti-Patterns, DevOps Solutions shows how to implement DevOps techniques in the kind of imperfect environments most developers work in. Part technology tutorial, part reference manual, and part psychology handbook, this practical guide shows you realistic ways to bring DevOps to your team when you don't have the flexibility to make sweeping changes in organizational structure.
To some extent, all organizations—even yours—suffer from poor development practices, garbled communications, and outdated legacy systems. The good news is DevOps can help you improve your processes. First, however, you'll need to recognize the core issues holding you back. This book empowers you to deliver DevOps with limited resources while navigating the office politics and entrenched mindsets that are all too common in actual workplaces.
Operations Anti-Patterns, DevOps Solutions offers clear steps for transforming development and communication. Using jargon-free language, this book describes incremental techniques that pay off immediately. Streamline your workflow, manage unplanned time, and build operational metrics. Whatever your issues, this book holds the keys to organizational success.
For team leaders and managers.
Jeffery D. Smith has been in the technology industry for over 15 years. He has managed DevOps transformations at the ad-tech firm Centro and the online ordering platform Grubhub.
A pragmatic guide to adopting DevOps practices progressively in every organization.
Zhuo Hong Wei, Indeed
A comprehensive guide to getting started with DevOps and integrating this culture in your company in the right manner.
Roman Levchenko, Microsoft Azure MVP
A truly inspiring book with real-world use cases and solutions. Really helpful for managers and technical leaders who want to drive change in their company.
Michele Adduci, OpenLimit SignCubes GmbH
NARRATED BY JULIE BRIERLEY
Chapter 1 The DevOps ingredients
Chapter 1 What DevOps is not
Chapter 1 CAMS, the pillars of DevOps
Chapter 2 The paternalist syndrome
Chapter 2 Introducing the gatekeepers
Chapter 2 Curing paternalism through automation
Chapter 2 Structuring code for automation
Chapter 2 Automating approvals
Chapter 2 Logging process
Chapter 3 Operational blindness
Chapter 3 Creating operational visibility
Chapter 3 Deciding what to measure
Chapter 3 Defining healthy metrics
Chapter 3 Making logging useful
Chapter 3 What should I be logging?
Chapter 3 The hurdles of log aggregation
Chapter 4 Data instead of information
Chapter 4 Widgets, the dashboard building blocks
Chapter 4 Giving context to your widgets
Chapter 4 Organizing your dashboard
Chapter 5 Quality as a condiment
Chapter 5 Testing structure
Chapter 5 Integration tests
Chapter 5 End-to-end tests
Chapter 5 Confidence in your test suite
Chapter 5 Restoring confidence in your test suite
Chapter 5 Feature flags
Chapter 5 Executing pipelines
Chapter 5 Managing the testing infrastructure
Chapter 5 Continuous deployment vs. continuous delivery
Chapter 6 Alert fatigue
Chapter 6 Defining on-call rotations
Chapter 6 Defining alert criteria
Chapter 6 Noisy alerts
Chapter 6 Staffing on-call rotations
Chapter 6 Compensating for being on call
Chapter 6 Tracking on-call happiness
Chapter 6 Providing other on-call tasks
Chapter 7 The empty toolbox
Chapter 7 Improvements made by automation
Chapter 7 Why organizations don’t automate more
Chapter 7 Staffing for automation and tooling
Chapter 7 Fixing your cultural automation problems
Chapter 7 The cost of manual work
Chapter 7 Defining your automation goals
Chapter 7 Reflecting automation as a priority with your staff
Chapter 7 Filling the skill-set gap
Chapter 7 But if I build it, I own it
Chapter 7 Approaching automation
Chapter 7 Designing for safety
Chapter 7 Complexity in tasks
Chapter 7 Automating simple tasks
Chapter 8 Off-hour deployments
Chapter 8 The layers of a deployment
Chapter 8 Making deployments routine affairs
Chapter 8 Staging will never be exactly like production
Chapter 8 Frequency reduces fear
Chapter 8 Handling failure in the layers of the deployment process
Chapter 8 Fleet rollbacks
Chapter 8 Database-level rollbacks
Chapter 8 Creating deployment artifacts
Chapter 8 Leveraging package management
Chapter 8 Configuration files in packages
Chapter 8 Automating your deployment pipeline
Chapter 9 Wasting a perfectly good incident
Chapter 9 Following the 24-hour rule
Chapter 9 Running the postmortem
Chapter 9 Running through the timeline
Chapter 9 Running through the timeline
Chapter 9 Defining action items and following up
Chapter 9 Documenting your postmortem
Chapter 10 Information hoarding: Only Brent knows
Chapter 10 Recognizing unintentional hoarders
Chapter 10 Abstraction vs. obfuscation
Chapter 10 Structuring your communication effectively
Chapter 10 Making your knowledge discoverable
Chapter 10 Creating learning rituals
Chapter 10 Creating learning rituals
Chapter 10 Using chat tools effectively
Chapter 11 Culture by decree
Chapter 11 Cultural rituals
Chapter 11 How does culture influence behavior?
Chapter 11 Sharing a culture
Chapter 11 An individual can change a culture
Chapter 11 Examining your company’s values
Chapter 11 Creating rituals
Chapter 11 Using rituals and language to change cultural norms
Chapter 11 Talent that matches your culture
Chapter 11 The obsession with senior engineers
Chapter 11 Interviewing candidates
Chapter 11 Interviewing candidates
Chapter 11 Evaluating candidates
Chapter 12 Too many yardsticks
Chapter 12 Team goals
Chapter 12 Consciousness around what you work on
Chapter 12 How to say no to a commitment
Chapter 12 Structuring your team’s work
Chapter 12 Unplanned work
Chapter 12 Dealing with unplanned work