<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Writing on Simon Mullis</title><link>http://www.simonmullis.com/writing/</link><description>Recent content in Writing on Simon Mullis</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Fri, 17 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://www.simonmullis.com/writing/index.xml" rel="self" type="application/rss+xml"/><item><title>Darmok, Brown M&amp;Ms, and the Bandwidth of Meaning</title><link>http://www.simonmullis.com/writing/darmok-bandwidth-of-meaning/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>http://www.simonmullis.com/writing/darmok-bandwidth-of-meaning/</guid><description>&lt;p&gt;Van Halen, brown M&amp;amp;Ms, 1980s.&lt;/p&gt;
&lt;p&gt;If you know the story, I don&amp;rsquo;t need to tell it. Three words and a decade just handed you the whole thing: the clause in the contract, the reason it wasn&amp;rsquo;t pettiness, the test hiding inside the sweets. You rebuilt all of it from almost nothing, because you and I happen to share the reference. That leap, from a fragment to the full picture, is the entire subject of this piece.&lt;/p&gt;</description></item><item><title>Compliance as an Inherited Property</title><link>http://www.simonmullis.com/writing/compliance-as-an-inherited-property/</link><pubDate>Thu, 16 Jul 2026 00:00:00 +0000</pubDate><guid>http://www.simonmullis.com/writing/compliance-as-an-inherited-property/</guid><description>&lt;p&gt;The scanner stopped us because of an uninstall command.&lt;/p&gt;
&lt;p&gt;We had built a small documentation-lookup tool for internal AI use at a global security vendor: a way for a language model to answer questions from official product documentation instead of guessing, and to ensure that everyone had the same chance equivalent (but not necessarily identical) answers from the LLM guided sessions. The reference material included a vendor&amp;rsquo;s published, supported uninstall procedure, which, like ten thousand other uninstall procedures, contains &lt;code&gt;rm -rf&lt;/code&gt;. The static security scanner in the review pipeline found the string, classified it as a critical finding, and the pull request stopped at InfoSec.&lt;/p&gt;</description></item><item><title>Right Finding, Wrong Fix</title><link>http://www.simonmullis.com/writing/right-finding-wrong-fix/</link><pubDate>Thu, 15 May 2025 00:00:00 +0000</pubDate><guid>http://www.simonmullis.com/writing/right-finding-wrong-fix/</guid><description>&lt;p&gt;A client of ours turned off a server one afternoon and stopped their partner payments cold. Not a nation-state, not ransomware. A scanner had flagged the box for a weak TLS configuration, the finding was accurate, someone acted on it quickly and responsibly, and a legacy system quietly holding up a chunk of their partner-transaction processing went dark along with it. Nobody in the room had known what ran through it. The security work was correct. The result was an outage.&lt;/p&gt;</description></item></channel></rss>