"value":"\n <p>You deploy a code change but it creates an issue.<\/p>\n\n<p>Maybe it breaks a feature, adds a bug or takes down an environment completely.<\/p>\n\n<p>How do you resolve it?<\/p>\n\n<p>Larger releases will sometimes have a roll back plan that details how to revert to the previous release.<\/p>\n\n<p>This can be difficult, especially for large releases and ones that change the database schema or values.<\/p>\n\n<p>Because of the amount of change, diagnosing an issue in a large release can take time.<\/p>\n\n<p>If it's been a while since the prior release, it can be some time since the code that introduced the issue was worked on - making it harder to fix.<\/p>\n\n<p>I prefer to do small releases and do them often.<\/p>\n\n<p>Some releases contain a single commit which was made only minutes since the previous release.<\/p>\n\n<p>This makes it easier to identify the issue, fix it and deploy a new version.<\/p>\n\n<p>No rolling back database changes or reverting to previous releases.<\/p>\n\n<p>Small, iterative deployments are less risky than large infrequent ones, easier to fix and make changes available to end users sooner.<\/p>\n\n ",
"format":"full_html",
"processed":"\n <p>You deploy a code change but it creates an issue.<\/p>\n\n<p>Maybe it breaks a feature, adds a bug or takes down an environment completely.<\/p>\n\n<p>How do you resolve it?<\/p>\n\n<p>Larger releases will sometimes have a roll back plan that details how to revert to the previous release.<\/p>\n\n<p>This can be difficult, especially for large releases and ones that change the database schema or values.<\/p>\n\n<p>Because of the amount of change, diagnosing an issue in a large release can take time.<\/p>\n\n<p>If it's been a while since the prior release, it can be some time since the code that introduced the issue was worked on - making it harder to fix.<\/p>\n\n<p>I prefer to do small releases and do them often.<\/p>\n\n<p>Some releases contain a single commit which was made only minutes since the previous release.<\/p>\n\n<p>This makes it easier to identify the issue, fix it and deploy a new version.<\/p>\n\n<p>No rolling back database changes or reverting to previous releases.<\/p>\n\n<p>Small, iterative deployments are less risky than large infrequent ones, easier to fix and make changes available to end users sooner.<\/p>\n\n ",