<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #code</title>
    <link>/tags/code/</link>
    <description>Recent bookmarks tagged #code</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:48 +0000</lastBuildDate>
    <item>
      <title>Computers can be understood - Made of Bugs</title>
      <link>https://blog.nelhage.com/post/computers-can-be-understood/</link>
      <description>Computers are complex, but need not be mysteries. Any question we care to ask can, in principle and usually even in practice, be answered. Unknown systems can be approached with curiosity and determination, not fear.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #code #computers #dev #software #work&lt;/p&gt;</description>
      <pubDate>Mon, 23 Feb 2026 20:04:03 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38337</guid>
      <category>code</category>
      <category>computers</category>
      <category>dev</category>
      <category>software</category>
      <category>work</category>
    </item>
    <item>
      <title>Atari Star Raiders Source Code : Atari : Free Download &amp; Streaming : Internet Archive</title>
      <link>https://archive.org/details/AtariStarRaidersSourceCode</link>
      <description>&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #atari #code #gaming #imported:pinboard #retro #tech&lt;/p&gt;</description>
      <pubDate>Fri, 16 Oct 2015 21:00:27 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:26015</guid>
      <category>atari</category>
      <category>code</category>
      <category>gaming</category>
      <category>imported:pinboard</category>
      <category>retro</category>
      <category>tech</category>
    </item>
    <item>
      <title>PICO-8: FANTASY GAME CONSOLE</title>
      <link>http://www.lexaloffle.com/pico-8.php</link>
      <description>PICO-8 is a fantasy console for making, sharing and playing tiny games and other computer programs. When you turn it on, the machine greets you with a shell for typing in Lua commands and provides simple built-in tools for creating your own cartridges.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #code #games #imported:pinboard #lua #pico #retro&lt;/p&gt;</description>
      <pubDate>Sun, 26 Jul 2015 20:27:48 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:25843</guid>
      <category>code</category>
      <category>games</category>
      <category>imported:pinboard</category>
      <category>lua</category>
      <category>pico</category>
      <category>retro</category>
    </item>
    <item>
      <title>Willa&#39;s World: The Six Most Common Species Of Code</title>
      <link>http://www.willa.me/2013/11/the-six-most-common-species-of-code.html?m=1</link>
      <description>&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #code #dev #imported:pinboard #programming #to:fb&lt;/p&gt;</description>
      <pubDate>Wed, 13 Nov 2013 16:44:13 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:24349</guid>
      <category>code</category>
      <category>dev</category>
      <category>imported:pinboard</category>
      <category>programming</category>
      <category>to:fb</category>
    </item>
    <item>
      <title>MI News Wire - State to Hold First-Ever &#39;Code Michigan&#39; Event</title>
      <link>http://www.michigan.gov/minewswire/0,4629,7-136-3452-308213--,00.html</link>
      <description>Code developers are invited to the state&#39;s first-ever Code Michigan event this October for an opportunity to build mobile applications and win cash prizes. The free &#34;civic coding&#34; event will also feature presentations from heavy-hitters in the technology industry.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #code #imported:pinboard #michigan&lt;/p&gt;</description>
      <pubDate>Tue, 23 Jul 2013 16:13:09 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:23969</guid>
      <category>code</category>
      <category>imported:pinboard</category>
      <category>michigan</category>
    </item>
    <item>
      <title>Write Code That Works by Reid Burke</title>
      <link>http://reidburke.com/2012/09/27/write-code-that-works/?awesm=reid.in_l6</link>
      <description>If you’re writing tests for code that’s rapidly changing, you’re going to spend more of your time writing tests instead of shipping features. For code that’s brand new, I typically only test-first a small amount of code and wait a while before hitting that green bar on a code coverage report.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #code #imported:pinboard #tests #work&lt;/p&gt;</description>
      <pubDate>Thu, 27 Sep 2012 20:51:07 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:32672</guid>
      <category>code</category>
      <category>imported:pinboard</category>
      <category>tests</category>
      <category>work</category>
    </item>
    <item>
      <title>Write Code That Works by Reid Burke</title>
      <link>http://reidburke.com/2012/09/27/write-code-that-works?awesm=reid.in_l6</link>
      <description>If you’re writing tests for code that’s rapidly changing, you’re going to spend more of your time writing tests instead of shipping features. For code that’s brand new, I typically only test-first a small amount of code and wait a while before hitting that green bar on a code coverage report.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #code #tests #work&lt;/p&gt;</description>
      <pubDate>Thu, 27 Sep 2012 20:51:07 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:22635</guid>
      <category>code</category>
      <category>tests</category>
      <category>work</category>
    </item>
    <item>
      <title>ArchiveTeam/warrior-code</title>
      <link>https://github.com/ArchiveTeam/warrior-code</link>
      <description>&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #archiveteam #at:aadl #code #git #imported:pinboard #via:textfiles #warrior&lt;/p&gt;</description>
      <pubDate>Thu, 24 May 2012 16:58:24 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:21879</guid>
      <category>archiveteam</category>
      <category>at:aadl</category>
      <category>code</category>
      <category>git</category>
      <category>imported:pinboard</category>
      <category>via:textfiles</category>
      <category>warrior</category>
    </item>
    <item>
      <title>Quick QR Codes In Django</title>
      <link>http://www.acedevs.com/blog/2011/07/25/quick-qr-codes-django/</link>
      <description>Creating QR codes is a quick and easy process using a few model signals and the PyQRNative port.  The hardest part of this implementation was finding a way to use the Django ContentFile object to save the generated QR code using our selected storage backend.  This was important because you would not have to worry about changes to your system architecture effecting your QR generation code.  An example would be moving from local filesystem storage to S3 using Django Storages (django-storages).&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #code #dango #images #imported:pinboard #qr #qrcodes #webdev&lt;/p&gt;</description>
      <pubDate>Tue, 22 May 2012 04:22:08 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:32821</guid>
      <category>code</category>
      <category>dango</category>
      <category>images</category>
      <category>imported:pinboard</category>
      <category>qr</category>
      <category>qrcodes</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Quick QR Codes In Django</title>
      <link>http://www.acedevs.com/blog/2011/07/25/quick-qr-codes-django</link>
      <description>Creating QR codes is a quick and easy process using a few model signals and the PyQRNative port.  The hardest part of this implementation was finding a way to use the Django ContentFile object to save the generated QR code using our selected storage backend.  This was important because you would not have to worry about changes to your system architecture effecting your QR generation code.  An example would be moving from local filesystem storage to S3 using Django Storages (django-storages).&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #code #dango #images #qr #qrcodes #webdev&lt;/p&gt;</description>
      <pubDate>Tue, 22 May 2012 04:22:08 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:21830</guid>
      <category>code</category>
      <category>dango</category>
      <category>images</category>
      <category>qr</category>
      <category>qrcodes</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Coding Horror: Learn to Read the Source, Luke</title>
      <link>http://www.codinghorror.com/blog/2012/04/learn-to-read-the-source-luke.html</link>
      <description>The transformative power of &#34;source always included&#34; in JavaScript is a major reason why I coined – and continue to believe in – Atwood&#39;s Law. Even if &#34;view source&#34; isn&#39;t built in (but it totally should be), you should demand access to the underlying source code for your stack. No matter what the documentation says, the source code is the ultimate truth, the best and most definitive and up-to-date documentation you&#39;re likely to find. This will be true forever, so the sooner you come to terms with this, the better off you&#39;ll be as a software developer.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #code #dev #development #imported:pinboard #viewsource #webdev&lt;/p&gt;</description>
      <pubDate>Thu, 17 May 2012 05:26:47 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:21786</guid>
      <category>code</category>
      <category>dev</category>
      <category>development</category>
      <category>imported:pinboard</category>
      <category>viewsource</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Of parser-fetishists and semi-colons | Christian Heilmann</title>
      <link>http://christianheilmann.com/2012/04/16/of-parser-fetishists-and-semi-colons/</link>
      <description>I think it is a sign that as developers we are either terribly bored or we are out of ideas when we start to go down to bickering about violating accepted ways of development. We should concentrate on building amazing tools and experiences for users out there rather than smugly trying to undo conventions we’ve been following for years now. The web standards movement was not about enforcing arbitrary code syntax on poor developers who now have to type a few keys more. It is about making code predictable, extensible and easy to explain to newcomers. Confusing these matters doesn’t help the cause of making a new generation of developers embrace the web as a platform. Don’t be that guy.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #amen #code #coding #imported:pinboard #javascript #standards #to:fb #twitter #webdev&lt;/p&gt;</description>
      <pubDate>Fri, 27 Apr 2012 01:15:19 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:32942</guid>
      <category>amen</category>
      <category>code</category>
      <category>coding</category>
      <category>imported:pinboard</category>
      <category>javascript</category>
      <category>standards</category>
      <category>to:fb</category>
      <category>twitter</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Of parser-fetishists and semi-colons | Christian Heilmann</title>
      <link>http://christianheilmann.com/2012/04/16/of-parser-fetishists-and-semi-colons</link>
      <description>I think it is a sign that as developers we are either terribly bored or we are out of ideas when we start to go down to bickering about violating accepted ways of development. We should concentrate on building amazing tools and experiences for users out there rather than smugly trying to undo conventions we’ve been following for years now. The web standards movement was not about enforcing arbitrary code syntax on poor developers who now have to type a few keys more. It is about making code predictable, extensible and easy to explain to newcomers. Confusing these matters doesn’t help the cause of making a new generation of developers embrace the web as a platform. Don’t be that guy.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #amen #code #coding #javascript #standards #to:fb #twitter #webdev&lt;/p&gt;</description>
      <pubDate>Fri, 27 Apr 2012 01:15:19 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:21514</guid>
      <category>amen</category>
      <category>code</category>
      <category>coding</category>
      <category>javascript</category>
      <category>standards</category>
      <category>to:fb</category>
      <category>twitter</category>
      <category>webdev</category>
    </item>
    <item>
      <title>#reviewth.is @github</title>
      <link>http://reviewth.is/</link>
      <description>GitHub gives us almost everything we need to do code reviews. Commit, file and line level comments, comment notifications, plus everything else that makes the GitHub experience great. The only thing missing is an easy way to initiate a review. If I want my code to be reviewed, I’ve got to go to GitHub, get the URL (and any other info), then compose an email to everyone I want to review it.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #code #dev #git #github #imported:pinboard #review&lt;/p&gt;</description>
      <pubDate>Sun, 04 Mar 2012 04:09:55 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:33123</guid>
      <category>code</category>
      <category>dev</category>
      <category>git</category>
      <category>github</category>
      <category>imported:pinboard</category>
      <category>review</category>
    </item>
    <item>
      <title>#reviewth.is @github</title>
      <link>http://reviewth.is</link>
      <description>GitHub gives us almost everything we need to do code reviews. Commit, file and line level comments, comment notifications, plus everything else that makes the GitHub experience great. The only thing missing is an easy way to initiate a review. If I want my code to be reviewed, I’ve got to go to GitHub, get the URL (and any other info), then compose an email to everyone I want to review it.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #code #dev #git #github #review&lt;/p&gt;</description>
      <pubDate>Sun, 04 Mar 2012 04:09:55 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:21078</guid>
      <category>code</category>
      <category>dev</category>
      <category>git</category>
      <category>github</category>
      <category>review</category>
    </item>
  </channel>
</rss>
