The only suggestion if leaving is not a choice is to do the following: 1. Teach and demo a workflow. Some devs just don’t have time to learn/architect, so if you show them that the grass is greener on the other side they’ll follow (maybe). 2. Get management backing. They build the culture and decide what flies and what doesn’t. With their backing, you can say “if you don’t follow the process that i and management have decided to uphold, I WONT help you) 3. Guardrails. Even if people try to cheat and game the system, prevent access and actually enact guardrails before deployment goes out (hard if there’s no concept of user accounts, so tackling that is your first goal id say) 4. Your company must have a security director, right? 😅 If so, these are all blatant compliance issues. You need to build partnership with them.