What "Shifting Left" in Software Really Means for Blameless DevOpsby@salkimmich
310 reads

What "Shifting Left" in Software Really Means for Blameless DevOps

tldt arrow
Read on Terminal Reader🖨️

Too Long; Didn't Read

There's a lot of talk these days around how to practice a "blameless culture" in software engineering. According to Google's SRE team, it's essentially sharing responsibility and awareness of an incident post-mortem in a constructive way. DevOps has made it relatively easy to ensure that the testing of the technology we are using can happen regularly and (at least in theory) smoothly, through the use of CI/CD - Continuous Integration and Continuous Deployment. But as your team shifts testing farther and farther in the development pipeline, you will begin to test and observe failures before they impact the customer experience.

Companies Mentioned

Mention Thumbnail
Mention Thumbnail
featured image - What "Shifting Left" in Software Really Means for Blameless DevOps
Sal Kimmich HackerNoon profile picture

@salkimmich

Sal Kimmich

About @salkimmich
LEARN MORE ABOUT @SALKIMMICH'S EXPERTISE AND PLACE ON THE INTERNET.
react to story with heart

RELATED STORIES

L O A D I N G
. . . comments & more!
Hackernoon hq - po box 2206, edwards, colorado 81632, usa