<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #software</title>
    <link>/tags/software/</link>
    <description>Recent bookmarks tagged #software</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:45 +0000</lastBuildDate>
    <item>
      <title>libvips</title>
      <link>https://www.libvips.org/</link>
      <description>libvips is a demand-driven, horizontally threaded image processing library. Compared to similar libraries, libvips runs quickly and uses little memory. libvips is licensed under the LGPL-2.1-or-later.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #images #software&lt;/p&gt;</description>
      <pubDate>Thu, 10 Sep 2026 18:27:23 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38747</guid>
      <category>dev</category>
      <category>images</category>
      <category>software</category>
    </item>
    <item>
      <title>stemdeckapp/stemdeck: Stemdeck is an modern stem extraction platform for musicians,producers and hobbyists, designed to isolate vocals, drums, bass, piano and guitar  for practice, transcription, remixing, and creative audio workflows through a modern and interactive interface</title>
      <link>https://github.com/stemdeckapp/stemdeck</link>
      <description>Stemdeck is an modern stem extraction platform for musicians,producers and hobbyists, designed to isolate vocals, drums, bass, piano and guitar for practice, transcription, remixing, and creative audio workflows through a modern and interactive interface&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #daw #music #software&lt;/p&gt;</description>
      <pubDate>Sun, 30 Aug 2026 00:25:55 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38724</guid>
      <category>daw</category>
      <category>music</category>
      <category>software</category>
    </item>
    <item>
      <title>Adobe is Cooked</title>
      <link>https://malejandro.com/reflections/en/adobe-is-cooked/</link>
      <description>What do you get when you spend the last decade and a half exploiting the very same people you were supposed to empower?&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #adobe #creative #photoshop #software #subscriptions&lt;/p&gt;</description>
      <pubDate>Thu, 23 Apr 2026 00:40:48 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38476</guid>
      <category>adobe</category>
      <category>creative</category>
      <category>photoshop</category>
      <category>software</category>
      <category>subscriptions</category>
    </item>
    <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>What, then, are we paying for? | Quinn Keast</title>
      <link>https://quinnkeast.com/writing/software-is-problem-ownership?ref=sidebar</link>
      <description>Paying for software isn’t paying for a solution. It’s paying for someone else to own a problem.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #ai #codegen #llms #software #tech&lt;/p&gt;</description>
      <pubDate>Fri, 06 Feb 2026 18:53:23 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38284</guid>
      <category>ai</category>
      <category>codegen</category>
      <category>llms</category>
      <category>software</category>
      <category>tech</category>
      <enclosure url="https://links.lmorchard.com/static/a811afc992aebb48608903d06693956a.jpg" type="image/jpeg"></enclosure>
    </item>
    <item>
      <title>Defeating a 40-year-old copy protection dongle – Dmitry Brant</title>
      <link>https://dmitrybrant.com/2026/02/01/defeating-a-40-year-old-copy-protection-dongle</link>
      <description>That’s right — this little device is what stood between me and the ability to run an even older piece of software that I recently unearthed during an expedition of software archaeology.&#xA;&#xA;For a bit more background, I was recently involved in helping a friend’s accounting firm to move away from using an extremely legacy software package that they had locked themselves into using for the last four decades.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #copyprotection #hacks #history #retro #software&lt;/p&gt;</description>
      <pubDate>Mon, 02 Feb 2026 04:11:27 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38273</guid>
      <category>copyprotection</category>
      <category>hacks</category>
      <category>history</category>
      <category>retro</category>
      <category>software</category>
    </item>
    <item>
      <title>How I estimate work as a staff software engineer</title>
      <link>https://www.seangoedecke.com/how-i-estimate-work/</link>
      <description>It is not possible to accurately estimate software work. Software projects spend most of their time grappling with unknown problems, which by definition can’t be estimated in advance. To estimate well, you must therefore basically ignore all the known aspects of the work, and instead try and make educated guesses about how many unknowns there are, and how scary each unknown is.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #software #staff #tech #work&lt;/p&gt;</description>
      <pubDate>Sun, 25 Jan 2026 22:26:07 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38223</guid>
      <category>dev</category>
      <category>software</category>
      <category>staff</category>
      <category>tech</category>
      <category>work</category>
      <enclosure url="https://links.lmorchard.com/static/d213af4fbbe776b65b04f7e46a1a9c73.jpg" type="image/jpeg"></enclosure>
    </item>
    <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>Resonant Computing Manifesto</title>
      <link>https://resonantcomputing.org/</link>
      <description>We suggest these five principles as a starting place:&#xA;&#xA;    Private: In the era of AI, whoever controls the context holds the power. While data often involves multiple stakeholders, people must serve as primary stewards of their own context, determining how it&#39;s used.&#xA;    Dedicated: Software should work exclusively for you, ensuring contextual integrity where data use aligns with your expectations. You must be able to trust there are no hidden agendas or conflicting interests.&#xA;    Plural: No single entity should control the digital spaces we inhabit. Healthy ecosystems require distributed power, interoperability, and meaningful choice for participants.&#xA;    Adaptable: Software should be open-ended, able to meet the specific, context-dependent needs of each person who uses it.&#xA;    Prosocial: Technology should enable connection and coordination, helping us become better neighbors, collaborators, and stewards of shared spaces, both online and off.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #manifestos #resonantsoftware #software #tech&lt;/p&gt;</description>
      <pubDate>Sat, 06 Dec 2025 20:32:29 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38084</guid>
      <category>dev</category>
      <category>manifestos</category>
      <category>resonantsoftware</category>
      <category>software</category>
      <category>tech</category>
      <enclosure url="https://links.lmorchard.com/static/9de0139e3fc013773cf0a8c6fc07036b.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>Software can be finished - Ross Wintle</title>
      <link>https://rosswintle.uk/2025/10/software-can-be-finished/?ref=sidebar</link>
      <description>There is a utopia where we write correct, bug-free, fast, secure, statically-built software with zero dependencies that does it’s job and will continue doing it’s job as long as the platform it’s written for endures. This feels like it should be a thing we strive for. It feels like a Good Thing (TM)&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #software&lt;/p&gt;</description>
      <pubDate>Thu, 16 Oct 2025 23:54:54 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37813</guid>
      <category>dev</category>
      <category>software</category>
      <enclosure url="https://links.lmorchard.com/static/4fd78a8326e4655d76868b6f586e7d45.jpg" type="image/jpeg"></enclosure>
    </item>
    <item>
      <title>Building the Hundred-Year Web Service with htmx - Alexander Petros - YouTube</title>
      <link>https://www.youtube.com/watch?v=lASLZ9TgXyc</link>
      <description>In the fast-moving JS ecosystem, keeping your software current can be a huge drain on resources. But what if there was way to write software that had minimal maintenance burden today and didn&#39;t inspire dread in the junior developers of tomorrow? Built into the web platform are all the capabilities necessary to create useful, networked services that last for decades—we just have to build in ways that takes advantage of them.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #future #js #software #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 17 Sep 2025 18:55:51 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37704</guid>
      <category>dev</category>
      <category>future</category>
      <category>js</category>
      <category>software</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/27b4660a11774c10327265d8b8c45b8c.jpg" type="image/jpeg"></enclosure>
    </item>
    <item>
      <title>You Want Technology With Warts</title>
      <link>https://entropicthoughts.com/you-want-technology-with-warts</link>
      <description>Every single wart that annoys us today, used to be a reasonable feature that someone relied on in their production code. Every wart we see today is a testament to the care the maintainers put into backward compatibility. If we choose a technology today, we want one that saves us from future maintenance by keeping our wartful code running – even if we don’t yet know it is wartful. The best indicator of this is whether the technology has warts today.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #future #software #sqlite #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 17 Sep 2025 18:55:13 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37703</guid>
      <category>dev</category>
      <category>future</category>
      <category>software</category>
      <category>sqlite</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Deluxe Paint on the Commodore Amiga</title>
      <link>https://stonetools.ghost.io/deluxepaint-amiga/</link>
      <description>VisiCalc on the Apple II. Lotus 1-2-3 on the IBM PC. Aldus PageMaker on the Macintosh. Deluxe Paint on the Amiga. The computer industry loves a “killer app,” that unique piece of software that compels consumers to purchase new computer hardware just for the privilege of running it. I can personally attest to Deluxe Paint as it compelled even my technophobic mother to buy into its potential.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #amiga #deluxepaint #retro #software&lt;/p&gt;</description>
      <pubDate>Wed, 17 Sep 2025 18:50:42 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37702</guid>
      <category>amiga</category>
      <category>deluxepaint</category>
      <category>retro</category>
      <category>software</category>
      <enclosure url="https://links.lmorchard.com/static/563e20d7212c518bcd6860293f1592a0.jpg" type="image/jpeg"></enclosure>
    </item>
    <item>
      <title>Kiro and the future of AI spec-driven software development - Kiro</title>
      <link>https://kiro.dev/blog/kiro-and-the-future-of-software-development/</link>
      <description>Generative and Agentic AI are poised to bring about a new wave of change. For the first time, there are tools developers can use to translate common-sense descriptions of desired program behavior into real, working systems. Many developers are using these tools already. Prompt-by-prompt, step-by step, they describe the system they want to build to AI code generators. This vibe coding approach to development has already been proven to be a powerful tool. But its power is limited because it is missing one important piece: a full vision of the bigger picture of what a program should do, and why it should do that.&#xD;&#xA;Enter specification.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #ai #codegen #llm #software #work&lt;/p&gt;</description>
      <pubDate>Wed, 16 Jul 2025 18:06:19 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29449</guid>
      <category>ai</category>
      <category>codegen</category>
      <category>llm</category>
      <category>software</category>
      <category>work</category>
      <enclosure url="https://links.lmorchard.com/static/b3f9cc5eca2dd1c0fadfbd419c0625d0.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>Kevin Webb: &#34;One of the best examples of LLM developer tooling I&#39;ve heard is from a team that supports software from the 80s-90s....&#34;</title>
      <link>https://bsky.app/profile/triangulator.org/post/3lqqgkkst2k2r</link>
      <description>One of the best examples of LLM developer tooling I&#39;ve heard is from a team that supports software from the 80s-90s. Their only source of documentation is *video interviews* with retired employees. So they feed them into transcription software and get summarized searchable notes out the other end.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #ai #computing #documentation #history #llms #software&lt;/p&gt;</description>
      <pubDate>Wed, 02 Jul 2025 04:31:42 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29472</guid>
      <category>ai</category>
      <category>computing</category>
      <category>documentation</category>
      <category>history</category>
      <category>llms</category>
      <category>software</category>
      <enclosure url="https://links.lmorchard.com/static/c22dd26c47cba71fd437c8f48335919b.jpg" type="image/jpeg"></enclosure>
    </item>
  </channel>
</rss>
