SRE is a practice that creates a bridge between operations and development. We discuss the roles and responsibilities of a site reliability engineer.

Wondering about development velocity? We explain what development velocity is, how to measure it, and how to balance the need for fast development and reliable products.

Summer means things are heating up. And things are definitely heating up at Blameless! We’ve been hard at work delivering new features and capabilities to our customers, so today I wanted to share a quick summary of all the latest. Here are 4 exciting product updates that enhance the way teams manage incidents and deliver reliable products to their customers.

Wondering about retrospective templates? We give a complete explanation of what a retrospective should include and best practices for using one.

Curious about incidents vs. problems? We explain the differences and how to handle each one. ‍

For the past four years, Catchpoint and various partners have been running a yearly SRE Survey. This year, Blameless is excited to partner with Catchpoint for the fifth annual survey. We want to hear from you if you are in a DevOps or SRE role or even if you work on reliability with some other title or role. There are tremendous, valuable learnings when we listen closely to practitioners.

Curious about the incident priority matrix? We discuss how to determine the impact and urgency of an incident, and how to create a matrix that helps prioritize incidents.

We discuss what software engineers and site reliability engineering are and explain their differences and their importance in the software development process.

As infrastructure engineers, there’s so much you can learn from studying past incidents. Luckily, Blameless Reliability Insights helps you find patterns that better equip you to deal with incidents to come. If you’ve never used it before and you’re curious what it looks like, you can watch a video demo here! These statistical insights give you the power to learn everything you can when something goes wrong. ‍

We explain how a DevOps team is structured, the roles and responsibilities within the team, and the balance between an individual contributor and the needs of the team.