> "We're not blaming one employee," said Chief Availability Officer Darryn Dieken<p>> "For whatever reason that we don't understand, the employee decided to do a global deployment," Dieken went on. The usual staggered approach was therefore bypassed.<p>> And the engineer who sidestepped Salesforce's carefully crafted policies and took down the platform? "We have taken action with that particular employee," said Dieken.<p>Holy contradiction, Batman!
This looks pretty bad on Salesforce's engineering culture.<p>1. They're still using manual processes where automation should be used.<p>2. They're using insufficiently robust scripts (Forgivable to a degree. Bugs happen)<p>3. They blame the individual rather than the process which allowed the individual to make this mistake.<p>4. They have their status page on the same infrastructure that the status page is reporting on.