Don’t Do This in Production
I find this a result of pervasive command and control structures which inevitably lead to low trust environment.<p>Something breaks, so the manager naturally thinks he must add a control that will prevent the person or a from ever being able to do it.<p>Very soon nobody can do anything without approvals by managers so far removed from actual decision that they don&#x27;t even know the names of components being subject to change. The change then must travel from the only people that know what the change is but are absolutely barred from ever seeing production environment to people that being so focused on operations don&#x27;t have time to actually understand what the change is.<p>Once you are being treated as untrustworthy it will show in the rest of your work. Why code correctly from the start when you are not deemed trustworthy to do it correctly and there is lengthy testing and approval process to make sure you are not going to bomb your company?<p>The correct step is to recognize, that introducing more controls can very soon lead to low trust between employees which is self-fulfilling prophecy. When you are not allowed to do something because you are not deemed trustworthy to do something, then soon you have no experience and then this serves as a proof that the initial decision was correct.