Failure is inevitable and a postmortem analysis, conducted in an open, blameless way, is the best way for IT techs and managers to learn from outages and near-misses. But when the "root cause" is determined to be "human error" (or worse, particular humans), the real causes and conditions are lost. In this insightful book, IT veteran Dave Zwieback shows you an approach for making postmortems blameless, so you can focus instead on addressing areas of fragility within systems and organizations. If you’re involved with assessing why something goes wrong on a project or at your company—as a system administrator, developer, team manager, or executive—the concrete steps in this guide will help you find a real solution that works. Recognize and mitigate the effects of stress during outages Learn how to communicate effectively in a charged, high-stakes postmortem conversation Collect the necessary data before the postmortem begins Focus on determining the actual causes and conditions of an outage Learn techniques for writing up a postmortem for either internal or external use
If your organization has embraced DevOps, you need people whose nonlinear career paths and wide-ranging interests will help you remove dysfunctional silos. But your efforts to hire DevOps practitioners aren't working. How do you unearth these DevOps creatures? Think like one. In this Web Ops & Performance report, Dave Zwieback describes a successful model for finding, hiring, and retaining talent based on the DevOps philosophy of Culture, Automation, Measurement, and Sharing. This concise report covers: Why the current recruiting model is broken How a culture of engagement gives candidates, recruiters, and hiring managers a common goal Finding "dark pools" of candidates via automation What attractive metrics to ditch in order to focus on what's business-critical Sharing the rich opportunities of failures as well as successes Download this free report to learn unorthodox but effective ways to find people who fit your company, and discover why prioritizing employee engagement and fulfillment leads to increased productivity, profits, and customer satisfaction.
Imagine you had to write a postmortem containing statements like these? "We were unable to resolve the outage as quickly as we would have hoped because our decision making was impacted by extreme stress." "We spent two hours repeatedly applying the fix that worked during the previous outage, only to find out that it made no difference in this one." "We did not communicate openly about an escalating outage that was caused by our botched deployment because we thought we were about to lose our jobs." While the above scenarios are entirely realistic, it's hard to find many postmortem write-ups that even hint at these "human factors." Their absence is, in part, due to the social stigma associated with publicly acknowledging their contribution to outages. And yet, people dealing with outages are clearly subject to physical exhaustion and psychological stress, not to mention impaired reasoning due to a host of cognitive biases. This report focuses on the effects and mitigation of stress and cognitive biases during outages and postmortems. This "human postmortem" is as important as the technical one, as it enables building more resilient systems and teams, and ultimately reduces the duration and severity of outages.
IT veteran Dave Zweiback describes an incident that threatens the very existence of a large financial institution, and the counterintuitive steps its leadership took to stop the downward spiral. Their novel approach is grounded in proven concepts from complexity science, resilience engineering, human factors, cognitive science, and organizational psychology. It allows us to identify the underlying conditions for failure, and make our systems (and organizations) safer and more resilient."--Page 4 of cover
If your organization has embraced DevOps, you need people whose nonlinear career paths and wide-ranging interests will help you remove dysfunctional silos. But your efforts to hire DevOps practitioners aren't working. How do you unearth these DevOps creatures? Think like one. In this Web Ops & Performance report, Dave Zwieback describes a successful model for finding, hiring, and retaining talent based on the DevOps philosophy of Culture, Automation, Measurement, and Sharing. This concise report covers: Why the current recruiting model is broken How a culture of engagement gives candidates, recruiters, and hiring managers a common goal Finding "dark pools" of candidates via automation What attractive metrics to ditch in order to focus on what's business-critical Sharing the rich opportunities of failures as well as successes Download this free report to learn unorthodox but effective ways to find people who fit your company, and discover why prioritizing employee engagement and fulfillment leads to increased productivity, profits, and customer satisfaction. Dave Zwieback has been managing large-scale, mission-critical infrastructure and teams for 17 years.
How Can DevOps Make You Antifragile? All complex computer systems eventually break, despite all of the heavy-handed, bureaucratic change-management processes we throw at them. But some systems are clearly more fragile than others, depending on how well they cope with stress. In this O’Reilly report, Dave Zwieback explains how the DevOps methodology can help make your system antifragile. Systems are fragile when organizations are unprepared to handle changing conditions. As generalists adept at several roles, DevOps practitioners adjust more easily to the fast pace of change. Rather than attempt to constrain volatility, DevOps embraces disorder, randomness, and impermanence to make systems even better. This concise report covers: Why Etsy, Netflix, and other antifragile companies constantly introduce volatility to test and upgrade their systems How DevOps removes the schism between developers and operations, enlisting developers to deploy as well as build Using continual experimentation and minor failures to make critical adjustments—and discover breakthroughs How an overreliance on measurement and automation can make systems fragile Why sharing increases trust, collaboration, and tribal knowledge Download this free report and learn how the DevOps philosophy of Culture, Automation, Measurement, and Sharing makes use of changing conditions and even embarrassing mistakes to help improve your system—and your organization. Dave Zwieback has been managing large-scale, mission-critical infrastructure and teams for 17 years.
In this series of hilarious confessions by "New Jersey's answer to Nick Hornby," learn how apologizing and coming to terms with past embarrassments can lead to compassion and maturity (Jonathan Mahler). Dave Bry is sorry. Very sorry. He's sorry to Wendy Metzger for singing the last verse of "Stairway to Heaven" into her ear while slow dancing in junior high school. He's sorry to Judy and Michael Gailhouse for letting their children watch The Amityville Horror when he babysat them. And he's sorry--especially, truly--that he didn't hear his cancer-ridden father call out for help one fateful afternoon. Things are different now. Dave's become a dad, too, and he's discovered a new compassion for the complicated man who raised him. And maybe if his 17-year-old self could meet his current self, he'd think twice before throwing beer cans on Jon Bon Jovi's lawn. Dave's apologies are at turns hysterically funny and profoundly moving, ultimately adding up to a deeply human, poignant and likable portrait of a man trying to come to grips with his past.
Ben is stuck. A development lead with a strong vision for how the intersection of development and operations at his office can be improved, he can’t help but feel overwhelmed and discouraged by common problems such as slow turnaround time, rushed and ineffective handover documentation, mounting technical debt, and a lagging QA process. What steps should Ben take to build the momentum needed to create positive changes within his company? In this unique business novel by Dave Harrison and Knox Lively, two DevOps professionals with years of diverse experience in the industry, you follow Ben as he solves work frustrations in order to adopt Agile, DevOps, and microservices architectures for his organization. Achieving DevOps addresses the “Now what?” moment many DevOps professionals face on their journey. The story provides you with the knowledge you need to navigate the internal political waters, build management support, show measurable results, and bring DevOps successfully into your organization. Come away with practical lessons and timeless business concepts. You’ll know how to effect change in a company from the bottom up, gain support, and instill a pattern of progressively building on success. Experience Ben’s progress vicariously in Achieving DevOps and bridge the gap between inspiration and the implementation of your own DevOps practices. Who This Book Is For Those serving as change agents who are working to influence and move their organizations toward a DevOps approach to software development and deployment: those working to effect change from the bottom up such as development leads, QA leads, project managers, and individual developers; and IT directors, CTOs, and others at the top of an organization who are being asked to lend their support toward DevOps implementation efforts
How Can DevOps Make You Antifragile? All complex computer systems eventually break, despite all of the heavy-handed, bureaucratic change-management processes we throw at them. But some systems are clearly more fragile than others, depending on how well they cope with stress. In this O’Reilly report, Dave Zwieback explains how the DevOps methodology can help make your system antifragile. Systems are fragile when organizations are unprepared to handle changing conditions. As generalists adept at several roles, DevOps practitioners adjust more easily to the fast pace of change. Rather than attempt to constrain volatility, DevOps embraces disorder, randomness, and impermanence to make systems even better. This concise report covers: Why Etsy, Netflix, and other antifragile companies constantly introduce volatility to test and upgrade their systems How DevOps removes the schism between developers and operations, enlisting developers to deploy as well as build Using continual experimentation and minor failures to make critical adjustments—and discover breakthroughs How an overreliance on measurement and automation can make systems fragile Why sharing increases trust, collaboration, and tribal knowledge Download this free report and learn how the DevOps philosophy of Culture, Automation, Measurement, and Sharing makes use of changing conditions and even embarrassing mistakes to help improve your system—and your organization. Dave Zwieback has been managing large-scale, mission-critical infrastructure and teams for 17 years.
Contains the complete and unabridged texts of: Dave Barry's guide to marriage and/or sex, Babies and other hazards of sex, Stay fit and healthy until you're dead, and Claw your way to the top.
Here are four of the funniest books from Dave Barry. Follow his handyman hints and see how easy it is to beat a home into submission; to earning raves as a lover and a parent; and discover the key steps to kicking, scratching and cheating your way up the corporate ladder.
Imagine you had to write a postmortem containing statements like these? "We were unable to resolve the outage as quickly as we would have hoped because our decision making was impacted by extreme stress." "We spent two hours repeatedly applying the fix that worked during the previous outage, only to find out that it made no difference in this one." "We did not communicate openly about an escalating outage that was caused by our botched deployment because we thought we were about to lose our jobs." While the above scenarios are entirely realistic, it's hard to find many postmortem write-ups that even hint at these "human factors." Their absence is, in part, due to the social stigma associated with publicly acknowledging their contribution to outages. And yet, people dealing with outages are clearly subject to physical exhaustion and psychological stress, not to mention impaired reasoning due to a host of cognitive biases. This report focuses on the effects and mitigation of stress and cognitive biases during outages and postmortems. This "human postmortem" is as important as the technical one, as it enables building more resilient systems and teams, and ultimately reduces the duration and severity of outages.
Som 22-årig står forfatteren med ansvaret for sin 8-årige lillebror. Med baggrund i 1980'ernes San Francisco får han skabt et kreativt, næsten trygt miljø for dem begge
This will help us customize your experience to showcase the most relevant content to your age group
Please select from below
Login
Not registered?
Sign up
Already registered?
Success – Your message will goes here
We'd love to hear from you!
Thank you for visiting our website. Would you like to provide feedback on how we could improve your experience?
This site does not use any third party cookies with one exception — it uses cookies from Google to deliver its services and to analyze traffic.Learn More.