"value":"\n <p>Whilst speaking with Dave Liddament last week, I remembered a slide I've seen in some of his previous presentations, such as <a href=\"https:\/\/www.daveliddament.co.uk\/talks\/effective-code-review\">Effective Code Review<\/a>.<\/p>\n\n<p>On the slide is a graph that shows the amount of time needed to fix a bug at different stages of the development lifecycle.<\/p>\n\n<p>Fixing a bug is the quickest and simplest when writing code.<\/p>\n\n<p>It's harder when being code reviewed or QA or client tested, more so when it's being released, and the most difficult and expensive once it's in the maintenance phase.<\/p>\n\n<p>Once it's live in the production environment, there's additional cleanup work to do which adds to the time and cost, and potentially damages your reputation.<\/p>\n\n<p>The sooner you can find a bug, the better.<\/p>\n\n<p>This is where tools such as automated testing, static analysis and CI pipelines shine and make it easier for you to find and fix potential bugs sooner.<\/p>\n\n ",
"format":"full_html",
"processed":"\n <p>Whilst speaking with Dave Liddament last week, I remembered a slide I've seen in some of his previous presentations, such as <a href=\"https:\/\/www.daveliddament.co.uk\/talks\/effective-code-review\">Effective Code Review<\/a>.<\/p>\n\n<p>On the slide is a graph that shows the amount of time needed to fix a bug at different stages of the development lifecycle.<\/p>\n\n<p>Fixing a bug is the quickest and simplest when writing code.<\/p>\n\n<p>It's harder when being code reviewed or QA or client tested, more so when it's being released, and the most difficult and expensive once it's in the maintenance phase.<\/p>\n\n<p>Once it's live in the production environment, there's additional cleanup work to do which adds to the time and cost, and potentially damages your reputation.<\/p>\n\n<p>The sooner you can find a bug, the better.<\/p>\n\n<p>This is where tools such as automated testing, static analysis and CI pipelines shine and make it easier for you to find and fix potential bugs sooner.<\/p>\n\n ",