<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" encoding="UTF-8" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:atom="http://www.w3.org/2005/Atom/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:fireside="http://fireside.fm/modules/rss/fireside">
  <channel>
    <fireside:hostname>web02.fireside.fm</fireside:hostname>
    <fireside:genDate>Tue, 16 Jun 2026 08:53:11 -0500</fireside:genDate>
    <generator>Fireside (https://fireside.fm)</generator>
    <title>Software Defined Interviews - Episodes Tagged with “Bad Code”</title>
    <link>https://www.softwaredefinedinterviews.com/tags/bad%20code</link>
    <pubDate>Tue, 13 Dec 2016 23:00:00 +0100</pubDate>
    <description>Deep discussions about technology, enterprise IT, and the like</description>
    <language>en-us</language>
    <itunes:type>episodic</itunes:type>
    <itunes:subtitle>Deep discussions about technology, enterprise IT, and the like</itunes:subtitle>
    <itunes:author>Software Defined Talk</itunes:author>
    <itunes:summary>Deep discussions about technology, enterprise IT, and the like</itunes:summary>
    <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/7/752ee20c-8e7a-4ce1-8214-0a3fef88215c/cover.jpg?v=7"/>
    <itunes:explicit>yes</itunes:explicit>
    <itunes:owner>
      <itunes:name>Software Defined Talk</itunes:name>
      <itunes:email>softwaredefinedinterviews@cote.wtf</itunes:email>
    </itunes:owner>
<itunes:category text="Technology"/>
<itunes:category text="News">
  <itunes:category text="Tech News"/>
</itunes:category>
<itunes:category text="Business">
  <itunes:category text="Management"/>
</itunes:category>
<item>
  <title>Episode 17: Ignoring bad code on purpose</title>
  <link>https://www.softwaredefinedinterviews.com/17</link>
  <guid isPermaLink="false">cce34e1c-fe72-49fd-85c5-6cd985ffd3a1</guid>
  <pubDate>Tue, 13 Dec 2016 23:00:00 +0100</pubDate>
  <author>Software Defined Talk</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/752ee20c-8e7a-4ce1-8214-0a3fef88215c/cce34e1c-fe72-49fd-85c5-6cd985ffd3a1.mp3" length="6434440" type="audio/mp3"/>
  <itunes:episode>17</itunes:episode>
  <itunes:title>Ignoring bad code on purpose</itunes:title>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>Software Defined Talk</itunes:author>
  <itunes:subtitle>Some reasons people would keep bad code, how management should think through it, and then some options for coping as needed.</itunes:subtitle>
  <itunes:duration>11:22</itunes:duration>
  <itunes:explicit>yes</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/7/752ee20c-8e7a-4ce1-8214-0a3fef88215c/episodes/c/cce34e1c-fe72-49fd-85c5-6cd985ffd3a1/cover.jpg?v=1"/>
  <description>&lt;p&gt;Sometimes you have to live with bad code. No one will let you change it. There’s many good and bad reasons, so make sure you’re consciously making the decision instead of accidentally doing it. I discuss some reasons people would keep bad code, how management should think through it, and then some options for coping as needed.&lt;/p&gt;

&lt;p&gt;It was &lt;a href="https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/" rel="nofollow noopener"&gt;Joel, back in 2000, who said not to re-write code&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I recorded this with a &lt;a href="http://amzn.to/2gIMFM3" rel="nofollow noopener"&gt;Mevo&lt;/a&gt;, hence the kind of echo'y noise. See the video &lt;a href="https://www.facebook.com/drunkandretired/videos/10154853806469169/" rel="nofollow noopener"&gt;over in Facebook where I LIVESTREAMED IT&lt;/a&gt;! &lt;/p&gt;
</description>
  <content:encoded>
    <![CDATA[<p>Sometimes you have to live with bad code. No one will let you change it. There’s many good and bad reasons, so make sure you’re consciously making the decision instead of accidentally doing it. I discuss some reasons people would keep bad code, how management should think through it, and then some options for coping as needed.</p>

<p>It was <a href="https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/" rel="nofollow noopener">Joel, back in 2000, who said not to re-write code</a>.</p>

<p>I recorded this with a <a href="http://amzn.to/2gIMFM3" rel="nofollow noopener">Mevo</a>, hence the kind of echo'y noise. See the video <a href="https://www.facebook.com/drunkandretired/videos/10154853806469169/" rel="nofollow noopener">over in Facebook where I LIVESTREAMED IT</a>!</p>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>Sometimes you have to live with bad code. No one will let you change it. There’s many good and bad reasons, so make sure you’re consciously making the decision instead of accidentally doing it. I discuss some reasons people would keep bad code, how management should think through it, and then some options for coping as needed.</p>

<p>It was <a href="https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/" rel="nofollow noopener">Joel, back in 2000, who said not to re-write code</a>.</p>

<p>I recorded this with a <a href="http://amzn.to/2gIMFM3" rel="nofollow noopener">Mevo</a>, hence the kind of echo'y noise. See the video <a href="https://www.facebook.com/drunkandretired/videos/10154853806469169/" rel="nofollow noopener">over in Facebook where I LIVESTREAMED IT</a>!</p>]]>
  </itunes:summary>
</item>
  </channel>
</rss>
