"value":"<p>You are working on a new feature.<\/p><p>You have two options.<\/p><p>You can commit and deploy a small amount of code every day, using feature flags when needed to show and hide the changes or ensure things aren't broken whilst being developed.<\/p><p>Or, you can wait and deploy everything at once.<\/p><p>Which is the less risky approach?<\/p><p>Which, if there is an issue, would make it easier to find and fix it?<\/p><p>Is it quicker to find an issue in tens of lines of code, or hundreds or thousands?<\/p><p>Is it simpler to disable a feature flag to hide the changes or roll back by reverting the commits, re-deploying the code and going through the same process again?<\/p><p>Which would you choose?<\/p>",
"format":"basic_html",
"processed":"<p>You are working on a new feature.<\/p><p>You have two options.<\/p><p>You can commit and deploy a small amount of code every day, using feature flags when needed to show and hide the changes or ensure things aren't broken whilst being developed.<\/p><p>Or, you can wait and deploy everything at once.<\/p><p>Which is the less risky approach?<\/p><p>Which, if there is an issue, would make it easier to find and fix it?<\/p><p>Is it quicker to find an issue in tens of lines of code, or hundreds or thousands?<\/p><p>Is it simpler to disable a feature flag to hide the changes or roll back by reverting the commits, re-deploying the code and going through the same process again?<\/p><p>Which would you choose?<\/p>",