There’s been a lot of talk about software ownership—but what does “owning code in production” really mean for developers day to day? Many development teams still reach for logs in production as the most familiar way to bridge the development environment with production.
Christine Yen (Honeycomb) makes the case that observability—and the skills to craft the right graphs and read them—benefits developers more than it does operators by examining several instances where well-informed devs can supercharge their development process, such as data-driven product decisions (or how to know more about what needs to be done than your PM), rewrites and migrations, feature flags and testing in production, and fine-grained performance analysis. Then, she lays out a series of steps to get your team from grepping unstructured text logs to outputting and analyzing well-structured traces. Instrumentation and observability aren’t all-or-nothing endeavors, and you’ll leave with an idea of the next step you can take to improve your ability to understand your production systems.
This session was recorded at the 2019 O'Reilly Velocity Conference in San Jose.
- Title: Observability for developers: How to get from here to there
- Release date: October 2019
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 0636920338406
You might also like
Software Engineering at Google
Today, software engineers need to know not only how to program effectively but also how to …
Designing Data-Intensive Applications
Data is at the center of many challenges in system design today. Difficult issues need to …
Head First Design Patterns, 2nd Edition
You know you don’t want to reinvent the wheel, so you look to design patterns—the lessons …
Fundamentals of Software Architecture
Salary surveys worldwide regularly place software architect in the top 10 best jobs, yet no real …