The tests+code review make sure people are doing basic due diligence on the code they're contributing. Meanwhile, SRE roles are defined to take up a bunch of t

The tests+code review make sure people are doing basic due diligence on the code they're contributing. Meanwhile, SRE roles are defined to take up a bunch of the brass tacks of making software storm-worthy... Are there aspects of good QA that you feel aren't hit by this combination? (Genuinely curious.)