Respond to comment

Author: ploeh

_posts/2024-07-15-the-end-of-trust.html

@@ -187,4 +187,20 @@ <h2 id="comments-header">
         </div>
         <div class="comment-date">2024-07-21 15:37 UTC</div>
     </div>
+
+    <div class="comment" id="0c1f8083882c4de8a11be963869cc098">
+        <div class="comment-author"><a href="/">Mark Seemann</a> <a href="#0c1f8083882c4de8a11be963869cc098">#</a></div>
+        <div class="comment-content">
+            <p>
+                Tyson, thank you for writing. I now realize that 'post mortem' was a poor choice of words on my part, since it implies that something went wrong. I should have written 'posterior' instead. I'll update the article.
+            </p>
+            <p>
+                I've been digging around a bit to see if I can find the article that originally made me aware of that option. I'm fairly sure that it wasn't <a href="https://itnext.io/optimizing-the-software-development-process-for-continuous-integration-and-flow-of-work-56cf614b3f59">Optimizing the Software development process for continuous integration and flow of work</a>, but that article, on the other hand, seems to be the source that other articles cite. It's fairly long, and also discusses other concepts; the relevant section here is the one called <em>Non-blocking reviews</em>.
+            </p>
+            <p>
+                An shorter overview of this kind of process can be found in <a href="https://thinkinglabs.io/articles/2023/05/02/non-blocking-continuous-code-reviews-a-case-study.html">Non-Blocking, Continuous Code Reviews - a case study</a>.
+            </p>
+        </div>
+        <div class="comment-date">2024-07-26 08:04 UTC</div>
+    </div>
 </div>