<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">I did want to call one thing out, though; <br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Jul 24, 2025, at 8:54, Nicholas Thompson <thompnickson2@gmail.com> wrote:</div><div><div dir="ltr"><div><div class="gmail-flex gmail-max-w-full gmail-flex-col gmail-grow"><div dir="auto" class="gmail-min-h-8 gmail-text-message gmail-relative gmail-flex gmail-w-full gmail-flex-col gmail-items-end gmail-gap-2 gmail-text-start gmail-break-words gmail-whitespace-normal gmail-[.text-message+&]:mt-5"><div class="gmail-flex gmail-w-full gmail-flex-col gmail-gap-1 empty:hidden gmail-items-end gmail-rtl:items-start"><div class="gmail-bg-token-message-surface gmail-relative gmail-max-w-[var(--user-chat-width,70%)] gmail-rounded-[18px] gmail-px-4 gmail-py-1.5 gmail-data-[multiline]:py-3"><div class="gmail-whitespace-pre-wrap"><br></div></div></div></div></div><i><b><span style="font-family:comic sans ms,sans-serif">NICK ASKS: I have argued with my complexity colleagues that their use of the term is extremely unfortunate and that they ought to use the term structure formation instead. Can you go up and down both sides of that argument?</span></b></i></div></div></div></blockquote><div><br></div><div>I believe that parses as: I don’t understand what you mean, so I take it that you probably don’t actually mean something. And therefore my response to what you are saying is an improvement on what you are saying.</div><div><br></div><div>Very human impulse, but I think an impulse that one often regrets not fighting off. Since I commit this error about once a day, it is never far from my mind. </div><div><br></div><div>Eric</div><div><br></div><div><br></div></div></body></html>