4 ms·
The president orders a massively impactful change and various processes in the company work to make sure it is safe before launching it. Sounds fine to me. If
by Jabbles 3y ago
The president orders a massively impactful change and various processes in the company work to make sure it is safe before launching it. Sounds fine to me.
If the president were told "this is risky, we have to verify that nothing will catch fire if we store it for more than 3 months" (or similar) I'm sure they would have agreed to proceed with caution, but still treat the matter as high priority.
- thiht 3y agoThis is not about safety, this is about ticking boxes. Boxes that make sense, but which are irrelevant compared to the potential impact of the change. For example, replacing the constant with a file parameter is important, but completely out of scope of the PR, and could lead to unexpected impacts. Sounds like there are enough things to QA with this small change that there’s no need to add other sources of potential bugs. The naming of the configuration key is also completely ridiculous and a huge waste of time.