"value":"\n <p>Code reviews are something that happens after the code has been written.<\/p>\n\n<p>Usually, a task is assigned to someone who completes it and makes the code available to their team members before it's merged.<\/p>\n\n<p>The problem is that if the implementation is wrong, it's already been written, which costs time and money.<\/p>\n\n<p>If the change needed to be rewritten or majorly changed before it could be merged, as well as being an awkward conversation, it would cost more time and money to do.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Instead of reviewing the code after it's been written, invest more time into planning how the implementation should work upfront.<\/p>\n\n<p>What potential solutions exist, and which would work best in this situation?<\/p>\n\n<p>Write technical design documents and, if needed, create a small proof of concept.<\/p>\n\n<p>Do this as a team and decide on the approach before any code is written and time or effort is spent.<\/p>\n\n<p>Then, the person working on the task will have a clearer path, and if you still want to review the code afterwards, you have something to compare it to.<\/p>\n\n ",
"format":"full_html",
"processed":"\n <p>Code reviews are something that happens after the code has been written.<\/p>\n\n<p>Usually, a task is assigned to someone who completes it and makes the code available to their team members before it's merged.<\/p>\n\n<p>The problem is that if the implementation is wrong, it's already been written, which costs time and money.<\/p>\n\n<p>If the change needed to be rewritten or majorly changed before it could be merged, as well as being an awkward conversation, it would cost more time and money to do.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Instead of reviewing the code after it's been written, invest more time into planning how the implementation should work upfront.<\/p>\n\n<p>What potential solutions exist, and which would work best in this situation?<\/p>\n\n<p>Write technical design documents and, if needed, create a small proof of concept.<\/p>\n\n<p>Do this as a team and decide on the approach before any code is written and time or effort is spent.<\/p>\n\n<p>Then, the person working on the task will have a clearer path, and if you still want to review the code afterwards, you have something to compare it to.<\/p>\n\n ",