Mistakes happen, things go wrong, for the vast majority of us a bug doesn't mean someone dies or lights go out or planes don't take off. For most of us here, th

Mistakes happen, things go wrong, for the vast majority of us a bug doesn't mean someone dies or lights go out or planes don't take off. For most of us here, the absolute worst case scenario is that a bug means a company nobody has ever heard of makes slightly less money for a few minutes or hours until it gets rolled back. Again, worst case. The average case is probably closer to a company nobody has ever heard of makes exactly the same amount of money but some arbitrary feature nobody asked for ships a day or two later because we spent time fixing this other thing instead. It's really hard to drive a balance between "pushing untested shitcode into prod multiple times a week" and "that ticket to change our CTA button color is done but now needs to go through 4 days of automated and manual testing." I think as an industry most of us are probably too far on the latter side of the spectrum in relation to the stakes of what we're actually doing day to day.