Respond to comment

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

@@ -229,4 +229,23 @@ <h2 id="comments-header">
         </div>
         <div class="comment-date">2024-07-29 14:29 UTC</div>
     </div>
+
+    <div class="comment" id="4655bc2aa6664d5ca10dfb069102bbfd">
+        <div class="comment-author"><a href="/">Mark Seemann</a> <a href="#4655bc2aa6664d5ca10dfb069102bbfd">#</a></div>
+        <div class="comment-content">
+            <p>
+                Jiehong, thank you for writing. Indeed, in <a href="/code-that-fits-in-your-head">Code That Fits in Your Head</a> I discuss how shared code ownership reduces the bus factor.
+            </p>
+            <p>
+                From this article and previous discussions I've had, I can see that the term <em>trust</em> is highly charged. People really don't like the notion that trust may be misplaced, or that mistrust, even, might be appropriate. I can't tell if it's a cultural bias of which I'm not aware. While English isn't my native language, I believe that I'm sufficiently acquainted with anglo-saxon culture to know of its most obvious quirks. Still, I'm sometimes surprised.
+            </p>
+            <p>
+                I admit that I, too, <em>first</em> consider whether I'm dealing with a deliberate adversary if I'm asked whether I trust someone, but soon after, there's a secondary interpretation that originates from normal human fallibility. I've <a href="/2023/03/20/on-trust-in-software-development">already written about that</a>: No, I don't trust my colleagues to be infallible, as I don't trust myself to be so.
+            </p>
+            <p>
+                Fortunately, it seems to me that the remedies that may address such concerns are the same, regardless of the underlying reasons.
+            </p>
+        </div>
+        <div class="comment-date">2024-08-06 05:57 UTC</div>
+    </div>
 </div>