This seems like a story out of time--I had to check the date to see it was 2024. I can't remember the last time I made software with releases and had QA folks r

This seems like a story out of time--I had to check the date to see it was 2024. I can't remember the last time I made software with releases and had QA folks run it through its paces. Maybe over 10 years ago I worked somewhere with releases each week or two, even there releases were almost daily by the time I left. Everywhere since, testing is automated and releases are continuous throughout the day so the developer (and peer reviewers) are the ones directly making the assessments whether a feature is fit for use by customers. I mean think about it, would a QA or business person be able to assess a security issue that a developer is aware of? We have to be responsible to raise the issues and have them understood by others, or just get them fixed (or satisfactorily mitigated) within the team. Another example is performance of operations, certain inefficient queries run frequently not only run slowly but can consume enough database CPU to basically make it unable to serve requests. The developer is the best person to be able to tell this in advance. The best situation to be in is to be able to both tune your processes and sense of safety to ship quickly but not unsafely. And if things do go wrong, don't blame a person but the processes in place and both technical and subjective safety measures and make changes accordingly.