<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>war-stories on Joe Stead</title><link>https://joestead.codes/tags/war-stories/</link><description>Recent content in war-stories on Joe Stead</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Thu, 04 Jun 2026 21:21:55 +0100</lastBuildDate><atom:link href="https://joestead.codes/tags/war-stories/index.xml" rel="self" type="application/rss+xml"/><item><title>A room full of right answers, and we were all wrong</title><link>https://joestead.codes/posts/everyone-is-right/</link><pubDate>Thu, 04 Jun 2026 09:00:00 +0100</pubDate><guid>https://joestead.codes/posts/everyone-is-right/</guid><description>&lt;p&gt;A few years ago I read a story of a software consultant raising concerns about software a defence company owned. He finds memory leaks all through it, flags them to the company, and gets a four-word reply: &amp;ldquo;Of course it leaks.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;No alarm. No fix on the way. The company was completely comfortable with a bug that in most systems would be a serious problem.&lt;/p&gt;
&lt;p&gt;Although I&amp;rsquo;ve never experienced a scenario exactly like this myself, there are parallels with something I recently experienced. I walked in with about as little context as that bug report carried, and the reaction threw me the same way.&lt;/p&gt;</description></item></channel></rss>