97 Things Every SRE Should Know


Book Description

Site reliability engineering (SRE) is more relevant than ever. Knowing how to keep systems reliable has become a critical skill. With this practical book, newcomers and old hats alike will explore a broad range of conversations happening in SRE. You'll get actionable advice on several topics, including how to adopt SRE, why SLOs matter, when you need to upgrade your incident response, and how monitoring and observability differ. Editors Jaime Woo and Emil Stolarsky, co-founders of Incident Labs, have collected 97 concise and useful tips from across the industry, including trusted best practices and new approaches to knotty problems. You'll grow and refine your SRE skills through sound advice and thought-provokingquestions that drive the direction of the field. Some of the 97 things you should know: "Test Your Disaster Plan"--Tanya Reilly "Integrating Empathy into SRE Tools"--Daniella Niyonkuru "The Best Advice I Can Give to Teams"--Nicole Forsgren "Where to SRE"--Fatema Boxwala "Facing That First Page"--Andrew Louis "I Have an Error Budget, Now What?"--Alex Hidalgo "Get Your Work Recognized: Write a Brag Document"--Julia Evans and Karla Burnett




97 Things Every SRE Should Know


Book Description

Site reliability engineering (SRE) is more relevant than ever. Knowing how to keep systems reliable has become a critical skill. With this practical book, newcomers and old hats alike will explore a broad range of conversations happening in SRE. You'll get actionable advice on several topics, including how to adopt SRE, why SLOs matter, when you need to upgrade your incident response, and how monitoring and observability differ. Editors Jaime Woo and Emil Stolarsky, co-founders of Incident Labs, have collected 97 concise and useful tips from across the industry, including trusted best practices and new approaches to knotty problems. You'll grow and refine your SRE skills through sound advice and thought-provokingquestions that drive the direction of the field. Some of the 97 things you should know: "Test Your Disaster Plan"--Tanya Reilly "Integrating Empathy into SRE Tools"--Daniella Niyonkuru "The Best Advice I Can Give to Teams"--Nicole Forsgren "Where to SRE"--Fatema Boxwala "Facing That First Page"--Andrew Louis "I Have an Error Budget, Now What?"--Alex Hidalgo "Get Your Work Recognized: Write a Brag Document"--Julia Evans and Karla Burnett




97 Things Every Cloud Engineer Should Know


Book Description

If you create, manage, operate, or configure systems running in the cloud, you're a cloud engineer--even if you work as a system administrator, software developer, data scientist, or site reliability engineer. With this book, professionals from around the world provide valuable insight into today's cloud engineering role. These concise articles explore the entire cloud computing experience, including fundamentals, architecture, and migration. You'll delve into security and compliance, operations and reliability, and software development. And examine networking, organizational culture, and more. You're sure to find 1, 2, or 97 things that inspire you to dig deeper and expand your own career. "Three Keys to Making the Right Multicloud Decisions," Brendan O'Leary "Serverless Bad Practices," Manases Jesus Galindo Bello "Failing a Cloud Migration," Lee Atchison "Treat Your Cloud Environment as If It Were On Premises," Iyana Garry "What Is Toil, and Why Are SREs Obsessed with It?", Zachary Nickens "Lean QA: The QA Evolving in the DevOps World," Theresa Neate "How Economies of Scale Work in the Cloud," Jon Moore "The Cloud Is Not About the Cloud," Ken Corless "Data Gravity: The Importance of Data Management in the Cloud," Geoff Hughes "Even in the Cloud, the Network Is the Foundation," David Murray "Cloud Engineering Is About Culture, Not Containers," Holly Cummins




97 Things Every Programmer Should Know


Book Description

Tap into the wisdom of experts to learn what every programmer should know, no matter what language you use. With the 97 short and extremely useful tips for programmers in this book, you'll expand your skills by adopting new approaches to old problems, learning appropriate best practices, and honing your craft through sound advice. With contributions from some of the most experienced and respected practitioners in the industry--including Michael Feathers, Pete Goodliffe, Diomidis Spinellis, Cay Horstmann, Verity Stob, and many more--this book contains practical knowledge and principles that you can apply to all kinds of projects. A few of the 97 things you should know: "Code in the Language of the Domain" by Dan North "Write Tests for People" by Gerard Meszaros "Convenience Is Not an -ility" by Gregor Hohpe "Know Your IDE" by Heinz Kabutz "A Message to the Future" by Linda Rising "The Boy Scout Rule" by Robert C. Martin (Uncle Bob) "Beware the Share" by Udi Dahan




97 Things Every Information Security Professional Should Know


Book Description

Whether you're searching for new or additional opportunities, information security can be vast and overwhelming. In this practical guide, author Christina Morillo introduces technical knowledge from a diverse range of experts in the infosec field. Through 97 concise and useful tips, you'll learn how to expand your skills and solve common issues by working through everyday security problems. You'll also receive valuable guidance from professionals on how to navigate your career within this industry. How do you get buy-in from the C-suite for your security program? How do you establish an incident and disaster response plan? This practical book takes you through actionable advice on a wide variety of infosec topics, including thought-provoking questions that drive the direction of the field. Continuously Learn to Protect Tomorrow's Technology - Alyssa Columbus Fight in Cyber Like the Military Fights in the Physical - Andrew Harris Keep People at the Center of Your Work - Camille Stewart Infosec Professionals Need to Know Operational Resilience - Ann Johnson Taking Control of Your Own Journey - Antoine Middleton Security, Privacy, and Messy Data Webs: Taking Back Control in Third-Party Environments - Ben Brook Every Information Security Problem Boils Down to One Thing - Ben Smith Focus on the WHAT and the Why First, Not the Tool - Christina Morillo




Kill It with Fire


Book Description

Kill It with Fire chronicles the challenges of dealing with aging computer systems, along with sound modernization strategies. How to survive a legacy apocalypse “Kill it with fire,” the typical first reaction to a legacy system falling into obsolescence, is a knee-jerk approach that often burns through tons of money and time only to result in a less efficient solution. This book offers a far more forgiving modernization framework, laying out smart value-add strategies and proven techniques that work equally well for ancient systems and brand-new ones. Renowned for restoring some of the world’s oldest, messiest computer networks to operational excellence, software engineering expert Marianne Bellotti distills key lessons and insights from her experience into practical, research-backed guidance to help you determine when and how to modernize. With witty, engaging prose, Bellotti explains why new doesn’t always mean better, weaving in illuminating case studies and anecdotes from her work in the field. You’ll learn: Where to focus your maintenance efforts for maximum impact and value How to pick the right modernization solutions for your specific needs and keep your plans on track How to assess whether your migrations will add value before you invest in them What to consider before moving data to the cloud How to determine when a project is finished Packed with resources, exercises, and flexible frameworks for organizations of all ages and sizes, Kill It with Fire will give you a vested interest in your technology’s future.




97 Things Every UX Practitioner Should Know


Book Description

Tap into the wisdom of experts to learn what every UX practitioner needs to know. With 97 short and extremely useful articles, you'll discover new approaches to old problems, pick up road-tested best practices, and hone your skills through sound advice. Working in UX involves much more than just creating user interfaces. UX teams struggle with understanding what's important, which practices they should know deeply, and what approaches aren't helpful at all. With these 97 concise articles, editor Dan Berlin presents a wealth of advice and knowledge from experts who have practiced UX throughout their careers. Bring Themes to Exploratory Research--Shanti Kanhai Design for Content First--Marli Mesibov Design for Universal Usability--Ann Chadwick-Dias Be Wrong on Purpose--Skyler Ray Taylor Diverse Participant Recruiting Is Critical to Authentic User Research--Megan Campos Put On Your InfoSec Hat to Improve Your Designs--Julie Meridian Boost Your Emotional Intelligence to Move from Good to Great UX--Priyama Barua




97 Things Every Java Programmer Should Know


Book Description

If you want to push your Java skills to the next level, this book provides expert advice from Java leaders and practitioners. You’ll be encouraged to look at problems in new ways, take broader responsibility for your work, stretch yourself by learning new techniques, and become as good at the entire craft of development as you possibly can. Edited by Kevlin Henney and Trisha Gee, 97 Things Every Java Programmer Should Know reflects lifetimes of experience writing Java software and living with the process of software development. Great programmers share their collected wisdom to help you rethink Java practices, whether working with legacy code or incorporating changes since Java 8. A few of the 97 things you should know: "Behavior Is Easy, State Is Hard"—Edson Yanaga “Learn Java Idioms and Cache in Your Brain”—Jeanne Boyarsky “Java Programming from a JVM Performance Perspective”—Monica Beckwith "Garbage Collection Is Your Friend"—Holly K Cummins “Java's Unspeakable Types”—Ben Evans "The Rebirth of Java"—Sander Mak “Do You Know What Time It Is?”—Christin Gorman




Implementing Service Level Objectives


Book Description

Although service-level objectives (SLOs) continue to grow in importance, there’s a distinct lack of information about how to implement them. Practical advice that does exist usually assumes that your team already has the infrastructure, tooling, and culture in place. In this book, recognized SLO expert Alex Hidalgo explains how to build an SLO culture from the ground up. Ideal as a primer and daily reference for anyone creating both the culture and tooling necessary for SLO-based approaches to reliability, this guide provides detailed analysis of advanced SLO and service-level indicator (SLI) techniques. Armed with mathematical models and statistical knowledge to help you get the most out of an SLO-based approach, you’ll learn how to build systems capable of measuring meaningful SLIs with buy-in across all departments of your organization. Define SLIs that meaningfully measure the reliability of a service from a user’s perspective Choose appropriate SLO targets, including how to perform statistical and probabilistic analysis Use error budgets to help your team have better discussions and make better data-driven decisions Build supportive tooling and resources required for an SLO-based approach Use SLO data to present meaningful reports to leadership and your users




Site Reliability Engineering


Book Description

The overwhelming majority of a software system’s lifespan is spent in use, not in design or implementation. So, why does conventional wisdom insist that software engineers focus primarily on the design and development of large-scale computing systems? In this collection of essays and articles, key members of Google’s Site Reliability Team explain how and why their commitment to the entire lifecycle has enabled the company to successfully build, deploy, monitor, and maintain some of the largest software systems in the world. You’ll learn the principles and practices that enable Google engineers to make systems more scalable, reliable, and efficient—lessons directly applicable to your organization. This book is divided into four sections: Introduction—Learn what site reliability engineering is and why it differs from conventional IT industry practices Principles—Examine the patterns, behaviors, and areas of concern that influence the work of a site reliability engineer (SRE) Practices—Understand the theory and practice of an SRE’s day-to-day work: building and operating large distributed computing systems Management—Explore Google's best practices for training, communication, and meetings that your organization can use