<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Duck on Ctrl &#43; Champagne</title>
    <link>/tags/duck/</link>
    <description>Recent content in Duck on Ctrl &#43; Champagne</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 06 Apr 2025 13:45:56 +0000</lastBuildDate>
    <atom:link href="/tags/duck/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Welcome to the Code Aviary: Where Ducks Debug and Canaries Die</title>
      <link>/posts/birds/</link>
      <pubDate>Sun, 06 Apr 2025 13:45:56 +0000</pubDate>
      <guid>/posts/birds/</guid>
      <description>&lt;h2 id=&#34;your-survival-guide-to-feathered-philosophies-in-software-development&#34;&gt;Your survival guide to feathered philosophies in software development&lt;/h2&gt;&#xA;&lt;h3 id=&#34;rubber-duck-debugging&#34;&gt;Rubber Duck Debugging&lt;/h3&gt;&#xA;&lt;p&gt;Alright, we&amp;rsquo;re starting easy and light for this one.&lt;/p&gt;&#xA;&lt;p&gt;It was popularised by the &lt;em&gt;Pragmatic Programmer&lt;/em&gt; written by Andrew Hunt and David Thomas (an alumnus of Imperial College London).&#xA;The idea is rather simple: instead of spending hours trying to debug something obscure,&#xA;explain the code line-by-line to an inanimate object - a rubber duck named Chucky maybe? - to help you work out what the problem is.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
