<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #craftsmanship</title>
    <link>/tags/craftsmanship/</link>
    <description>Recent bookmarks tagged #craftsmanship</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:52 +0000</lastBuildDate>
    <item>
      <title>Software craftsmanship is dead</title>
      <link>https://www.pcloadletter.dev/blog/craftsmanship-is-dead/</link>
      <description>I feel like it&#39;s been forever since I had a conversation about craftsmanship on the job. It&#39;s possible I have just found myself in the wrong places time and time again.&#xA;&#xA;Or maybe, and this is something I really fear, maybe the people who truly focus on the craft of software engineering are retiring or getting run off.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #craftsmanship #dev #software #work&lt;/p&gt;</description>
      <pubDate>Thu, 08 Jan 2026 04:07:26 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38180</guid>
      <category>craftsmanship</category>
      <category>dev</category>
      <category>software</category>
      <category>work</category>
    </item>
    <item>
      <title>Read-optimize Your Source Code - Brendel Consulting</title>
      <link>http://www.brendel.com/consulting/blog/2009/06/read-optimized-source-code.html</link>
      <description>&#34;In fact, I claim that if you don&#39;t take those rules to heart in your own source code then you are either unprofessional, lazy, not a team-player, or all of the above. If you as a software developer take pride in your professionalism and quality of your work then you have to consider that it is not only the achieved functionality for which you are being paid: The code you produce in almost all cases becomes property of your employer, and thus, the code itself also a product (and actually the most important product) you deliver. And how useful that code if for the team who has to work with it is what really determines its value.&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #code #craftsmanship #programming #source #via:jzawodny #writing&lt;/p&gt;</description>
      <pubDate>Tue, 16 Jun 2009 05:32:47 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:12340</guid>
      <category>code</category>
      <category>craftsmanship</category>
      <category>programming</category>
      <category>source</category>
      <category>via:jzawodny</category>
      <category>writing</category>
    </item>
    <item>
      <title>Software Craftsmanship 2009 - Home</title>
      <link>http://parlezuml.com/softwarecraftsmanship</link>
      <description>&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #conferences #craftsmanship #london #master #programming #skills #software&lt;/p&gt;</description>
      <pubDate>Tue, 02 Dec 2008 16:00:16 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:11713</guid>
      <category>conferences</category>
      <category>craftsmanship</category>
      <category>london</category>
      <category>master</category>
      <category>programming</category>
      <category>skills</category>
      <category>software</category>
    </item>
    <item>
      <title>Mark Bernstein: NeoVictorian Computing 5: Brushstrokes</title>
      <link>http://markbernstein.org/Sep0701/Brushstrokes.html</link>
      <description>&#34;We should expect to learn. Sophisticated tools require study and effort, and they repay that effort by letting us do things we could not do otherwise&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #compsci #craftsmanship #programming #software #work&lt;/p&gt;</description>
      <pubDate>Wed, 24 Oct 2007 18:03:38 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:9849</guid>
      <category>compsci</category>
      <category>craftsmanship</category>
      <category>programming</category>
      <category>software</category>
      <category>work</category>
    </item>
  </channel>
</rss>
