Programmings big dirty secret is that everyone has, at some point in their career, broken something big. Big like, wiping the full production database on their first day of work, killing the live application while multiple sales people are showing it to clients, or bringing down half the internet by passing on the wrong piece of data. Oops. There are a million reasons why things go wrong, and not all are completely avoidable. But having a good setup for testing new code can at least mitigate some of the worst errors. Traditionally, deploying new code to a website or application…
This story continues at The Next Web
