Book Image

Real-World SRE

By : Pavlos Ratis, Nat Welch
Book Image

Real-World SRE

By: Pavlos Ratis, Nat Welch

Overview of this book

Real-World SRE is the go-to survival guide for the software developer in the middle of catastrophic website failure. Site Reliability Engineering (SRE) has emerged on the frontline as businesses strive to maximize uptime. This book is a step-by-step framework to follow when your website is down and the countdown is on to fix it. Nat Welch has battle-hardened experience in reliability engineering at some of the biggest outage-sensitive companies on the internet. Arm yourself with his tried-and-tested methods for monitoring modern web services, setting up alerts, and evaluating your incident response. Real-World SRE goes beyond just reacting to disaster—uncover the tools and strategies needed to safely test and release software, plan for long-term growth, and foresee future bottlenecks. Real-World SRE gives you the capability to set up your own robust plan of action to see you through a company-wide website crisis. The final chapter of Real-World SRE is dedicated to acing SRE interviews, either in getting a first job or a valued promotion.
Table of Contents (16 chapters)
Real-World SRE
Contributors
Preface
Other Books You May Enjoy
Index

Finding projects


If you join an existing team or are a junior engineer, your first projects may be dictated to you. Often, an organization will hire someone because they have a need that their current team isn't meeting. As you complete the task you were hired for, you'll probably want to start finding projects you want to fix or improve. This chapter will generally focus on starting new projects, but do not underestimate the value of helping out with someone else's work. A great way to learn and grow is to write software with others. By being part of a group trying to implement a piece of software, you often learn about their processes and needs. For example, I found out about a project's broken testing environment because I offered to pick up a small bug that needed fixing. The tests had been broken for months and either no one noticed or no one mentioned it.

All of that aside, if you're looking to start a new project, instead of joining an existing one, you will need to find a problem...