It’s deployment day, and you feel that familiar dread that comes with knowing that your code is going into production. You whisper a silent prayer: “Please God, don’t let my code take down production.” As the servers are restarted you feel the pit in your stomach growing. Beads of sweat roll down your forehead as you watch the logs, check the alarms, and monitor the sales.
If this sounds familiar, you may be working in an environment that practices fear-driven development.
There are two critical factors that need to be present in an enterprise for fear-driven development to take hold.
