2 ms·
Why? A mistake is a mistake but if you are bypassing policies to cowboy code then you deserve to be fired.
by spoonjim 5y ago
Why? A mistake is a mistake but if you are bypassing policies to cowboy code then you deserve to be fired.
- carlmr 5y agoThe question to me is not what was written in policy, rather what was normal in the engineering culture at that company. They say they have a process for this, but how many engineers were following this process? How many fixes were deployed as EBFs before? How common was it to use EBFs with existing tried-and-true scripts? How clear is it in this manual process what you're doing? How much pressure was there to do an EBF? Depending on the surrounding culture around this, which I can't know from outside, he could be anything from a scapegoat to a cowboy coder. If you fire scapegoats you don't fix the issue.
- ckdarby 5y agoThat is not an acceptable stance at an organisation of this size. Policies don't just exist on paper they're enforced through the process. No employee should just be able to "cowboy" a solution like this. How does someone bypass the policy if the only way to get your code out is through pipeline? That pipeline required other individuals in the company to approve. Even the most basic regulation that Salesforce would have to deal with talks about speration of roles & responsibilities. Great, a dev can approve their code to go out but ops is responsible for deploying that out to production for this very reason.