There’s a production issue, all hands on deck…

You probably have the freedom to do whatever it takes to correct the problem, most likely skimping on following version control best practices, intense regression testing, deep dive into root-cause analysis, etc.

Great, issue, resolved. Freedom to take action without the normal hindrances, red tape and overhead.

Until…

Another production problem is discovered…

Then the questions are a flying and the control handcuffs are slapped back:

“why did you?”

“how could you?”

“under no circumstance, can we do that again”

“4 sign-offs are needed, no matter what”

“Hey Milton, put down your red stapler, you’re now in charge of version control and CI/CD”.

If you’ve been around development long enough, you may have ran into similar situations.

If you’re looking for a better way to manage this process, and put Milton back in the basement, you might want to check out: Mastering Salesforce DevOps by Andrew Davis where he discusses ideas and concepts to achieve both control and deployment freedom.