> My job is simply to make sure that software is releasable given the business’ definition of what is releasable, and to improve it in the future in such ways t

> My job is simply to make sure that software is releasable given the business’ definition of what is releasable, and to improve it in the future in such ways the business sees fit. Building on that concept, it is even more important that it is not my job as an engineer to assess the risk of releasing a piece of software to the public as I, and other engineers are (typically) unqualified to do so. "My job is simply": These words have no place in the mouth of any engineer. "it is not my job as an engineer to assess the risk": That is literally your job as an engineer. "Releasing imperfect software is just the nature of our lives.": This is a thing that happens, sometimes by accident and sometimes deliberately (hopefully more the former than the latter). Why would you deliberately release imperfect software? Because it is sufficient for a need at the time, and you assessed the risk that it created and found that releasing it in an imperfect state was better than delaying for a perfect (possibly unattainable) state. Note that key step: you addressed the risk. You. Your responsibility as an engineer. If you don't want to do those things, stop calling yourself an engineer. If you do keep calling yourself an engineer and continue to deliberately fall short of your responsibilities, kindly fuck off.