> Despite the annoyance of the security team and other developers who felt threatened by his work Depending on what he did the security team may have rightfull

> Despite the annoyance of the security team and other developers who felt threatened by his work Depending on what he did the security team may have rightfully had issues with the work. I've seen it time and time again. Someone automates something, the tool gets released to users and it's full of SQLi, XSS, and RCE vulnerabilities, sometimes opening up a once protected data-set or systems to company or Internet wide exposure. It's shadow IT/Dev work like this which tends to be responsible for the most security incidents.