<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="https://www.yellowduck.be/pretty-atom-feed-v3.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <link href="https://www.yellowduck.be" rel="alternate"/>
  <link href="https://www.yellowduck.be/posts/feed" rel="self"/>
  <author>
    <name>Pieter Claerhout</name>
    <email>pieter@yellowduck.be</email>
  </author>
  <id>https://www.yellowduck.be/posts/feed</id>
  <title>🐥 YellowDuck.be</title>
  <updated>2026-08-11T17:00:00Z</updated>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/designing-partitioning-you-dont-have-to-babysit" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Partitioning can be a double-edged sword. When done improperly, it leads to operational headaches and poor performance. Ruslan Tolkachev addresses these issues by arguing against using &lt;code&gt;created_at&lt;/code&gt; as a partition key. Instead, he suggests partitioning by primary key, leveraging the growth patterns of data without leaking the partition key into application code. Tolkachev illustrates common pitfalls, like partitions not pruned due to the absence of the partition key in queries. He emphasizes the importance of automatic management of partition boundaries, advocating for a service that can dynamically adjust to traffic patterns. This approach allows for query efficiency while sidestepping the errors of static partition management. Ultimately, the article delivers valuable insights into database architecture, encouraging practices that enhance performance without added operational burden.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://explainanalyze.com/p/designing-partitioning-you-dont-have-to-babysit/&quot;&gt;Continue reading on &lt;strong&gt;explainanalyze.com&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/database&quot;&gt;#database&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/devops&quot;&gt;#devops&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-11T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/designing-partitioning-you-dont-have-to-babysit</id>
    <title>🔗 Designing partitioning you don&apos;t have to babysit</title>
    <updated>2026-08-11T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/how-to-stop-claude-from-saying-load-bearing" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Absolutely ripping your hair out reading Claude referring to everything as “honest takes” and &quot;load-bearing seams&quot;? There’s a way to turn this frustration into something laughable or simply fix Claude&apos;s vocabulary. Johanna Larsson introduces the &lt;code&gt;MessageDisplay&lt;/code&gt; hook to make your interactions with Claude more enjoyable. By writing a small Python script that includes clever replacements, such as changing &quot;load-bearing&quot; to &quot;cooked,&quot; users can customize Claude&apos;s responses. The article provides a comprehensive setup guide, including where to place the script and how to integrate it into Claude&apos;s settings. This allows users to start fresh with a new, more entertaining dialog on their journey with AI.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://jola.dev/posts/how-to-stop-claude-from-saying-load-bearing&quot;&gt;Continue reading on &lt;strong&gt;jola.dev&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/python&quot;&gt;#python&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/tools&quot;&gt;#tools&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/ai&quot;&gt;#ai&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-11T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/how-to-stop-claude-from-saying-load-bearing</id>
    <title>🔗 How to stop Claude from saying load-bearing</title>
    <updated>2026-08-11T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/what-is-good-code" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;What defines good code? It’s more than just coding standards; it’s the foundation protecting user needs and system integrity. Mike Zornek highlights key attributes of good code: it solves problems, is accurate, reliable, and secure, and is easy to understand and change. He argues that good code addresses user goals, avoids unnecessary complexities, and promotes maintainability. In an era where software faces increasing entropy, adopting practices like testing, user feedback, and documentation becomes essential. Zornek emphasizes that while not all code needs to be perfect, the longer production practices are postponed, the harder it is to establish a culture of good coding. For further reading, he recommends &quot;A Philosophy of Software Design&quot; by John Ousterhout, an insightful resource on managing software complexity.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://mikezornek.com/posts/2026/7/what-is-good-code/&quot;&gt;Continue reading on &lt;strong&gt;mikezornek.com&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/development&quot;&gt;#development&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/testing&quot;&gt;#testing&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-11T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/what-is-good-code</id>
    <title>🔗 What is good code?</title>
    <updated>2026-08-11T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/top-10-backend-frameworks-for-enterprise-development-in-2026" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;In 2026, choosing a backend framework is more nuanced than ever. Enterprise teams now balance performance, ecosystem maturity, and developer availability against long-term costs. The guide delves into the top frameworks crucial for enterprise development this year. It outlines the strengths and limitations of each framework, guiding teams on aligning choices with their specific constraints rather than popular trends.&lt;/p&gt;
&lt;p&gt;Among the contenders, Spring Boot remains dominant due to its vast ecosystem, but alternatives like Quarkus and FastAPI offer compelling advantages in speed and memory efficiency. For Python enthusiasts, Django and FastAPI cater to varying needs, emphasizing security and async capabilities. This year’s choices underscore the importance of matching frameworks to organizational goals, serving both current needs and future demands with a focus on scalability, security, and developer capacity.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://blog.vaadin.com/enterprise-backend-frameworks&quot;&gt;Continue reading on &lt;strong&gt;blog.vaadin.com&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/development&quot;&gt;#development&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/python&quot;&gt;#python&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/django&quot;&gt;#django&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/java&quot;&gt;#java&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-10T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/top-10-backend-frameworks-for-enterprise-development-in-2026</id>
    <title>🔗 Top 10 backend frameworks for enterprise development in 2026</title>
    <updated>2026-08-10T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/ai-coding-tip-027-force-code-standards" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Style errors double when nobody enforces them. Maximiliano Contieri outlines a critical aspect of AI coding: enforcing standards. A CodeRabbit analysis revealed that AI-generated code contains about 1.7 times more defects than human-written code, particularly in the areas of naming and style consistency. Instead of relying on human memory to remember coding standards, Contieri advocates for integrating machine-checkable rules through hooks and validators. This can block violations before any human review occurs, allowing developers to focus on design rather than mechanical checks. With each violation logged as a rule, the enforcement grows stricter over time, promising a measurable drop in defects and allowing for faster reviews. This shift emphasizes the need for automation in maintaining code quality.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://maxicontieri.substack.com/p/ai-coding-tip-027-force-code-standards&quot;&gt;Continue reading on &lt;strong&gt;maxicontieri.substack.com&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/development&quot;&gt;#development&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/ai&quot;&gt;#ai&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/testing&quot;&gt;#testing&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-10T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/ai-coding-tip-027-force-code-standards</id>
    <title>🔗 AI coding tip 027 - Force code standards</title>
    <updated>2026-08-10T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/jurassic-park-computers-in-excruciating-detail" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;What does the technology in &lt;em&gt;Jurassic Park&lt;/em&gt; reveal about the era it was made? Fabien Sanglard delves into the specifics of every computer and software showcased in the film. From the &lt;em&gt;Apple Powerbook 100&lt;/em&gt; to &lt;em&gt;SGI IRIS Crimson&lt;/em&gt;, he breaks down the specs and functionalities of these machines, noting how they contributed to the movie&apos;s iconic scenes. The article highlights the impressive real-time 3D animations powered by &lt;em&gt;SGI workstations&lt;/em&gt; and discusses the hefty value of the computer hardware loaned during production, which rose to $4 million in today’s dollars. By examining the devices in the chaos of the Control Room, Sanglard provides a refreshing take on a nostalgic element of the film that many may overlook. Whether it’s the monitors or the personal digital assistants, each piece tells a story about the technology of the early &apos;90s.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://fabiensanglard.net/jurrasic_park_computers/index.html&quot;&gt;Continue reading on &lt;strong&gt;fabiensanglard.net&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-10T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/jurassic-park-computers-in-excruciating-detail</id>
    <title>🔗 Jurassic Park computers in excruciating detail</title>
    <updated>2026-08-10T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/are-we-offloading-too-much-of-our-thinking-to-ai" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;This article examines the growing trend of offloading cognitive tasks to AI, including both trivial and complex decisions. Yennie Jun illustrates this by referencing Ken Liu&apos;s short story &quot;The Perfect Match,&quot; where the protagonist relies on an AI assistant for personal choices, reflecting a concerning loss of autonomy. The piece discusses real-life encounters with individuals who let AI dictate their thoughts and decisions, raising questions about the impact of this dependency on critical thinking and originality. Jun encourages a balance between leveraging AI for efficiency and retaining our own thought processes, exploring how automation in daily tasks might enhance productivity versus leading to lazy thinking. Ultimately, the article provokes a deeper introspection about the consequences of allowing AI to make decisions that shape our identities and desires.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.artfish.ai/p/offloading-thinking-to-ai&quot;&gt;Continue reading on &lt;strong&gt;www.artfish.ai&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/development&quot;&gt;#development&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/ai&quot;&gt;#ai&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-09T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/are-we-offloading-too-much-of-our-thinking-to-ai</id>
    <title>🔗 Are we offloading too much of our thinking to AI?</title>
    <updated>2026-08-09T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/lobste-rs-is-now-running-on-sqlite" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Lobste.rs has officially migrated from MariaDB to SQLite. This decision, which began in August 2018 with plans initially focused on PostgreSQL, culminated successfully over the past weekend. The new architecture has shown performance improvements, including reduced CPU and memory usage, making the site feel snappier. The Lobsters Rails application now operates on a single VPS with an SQLite database file of approximately 3.8GB, supplemented by a cache and queue database, and a rack_attack database. The migration PR optimized the code significantly, reflecting a modern approach to server management with minimal resources. This case study serves as a potent reminder of how effective SQLite can be for smaller applications in 2026.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://simonwillison.net/2026/Jul/14/lobsters-sqlite/#atom-everything&quot;&gt;Continue reading on &lt;strong&gt;simonwillison.net&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/laravel&quot;&gt;#laravel&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/database&quot;&gt;#database&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/sqlite&quot;&gt;#sqlite&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-09T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/lobste-rs-is-now-running-on-sqlite</id>
    <title>🔗 Lobste.rs is now running on SQLite</title>
    <updated>2026-08-09T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/i-couldve-rickrolled-the-entire-fifa-world-cup-all-i-needed-was-my-id" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;What if a simple registration process could expose live broadcasts of one of the biggest sporting events in the world? In this article, the author outlines a shocking incident where a flaw in FIFA&apos;s security allowed access to the Streaming Management panel for the FIFA World Cup 2026. By just registering as a football agent, they gained entry to live match feeds, RTMP ingest URLs, and even the ability to manipulate match statistics. This breach highlighted a critical failure in server-side security, where backend APIs trusted authenticated users without proper role checks. Despite multiple attempts to report the issue to FIFA and related entities, the author faced significant hurdles in getting the problem acknowledged. Ultimately, the vulnerability was patched quickly, but FIFA did not respond or thank the whistleblower, raising concerns about security practices in mega sporting events.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://bobdahacker.com/blog/fifa-hack&quot;&gt;Continue reading on &lt;strong&gt;bobdahacker.com&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/auth&quot;&gt;#auth&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-09T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/i-couldve-rickrolled-the-entire-fifa-world-cup-all-i-needed-was-my-id</id>
    <title>🔗 I could&apos;ve rickrolled the entire FIFA World Cup. All I needed was my ID.</title>
    <updated>2026-08-09T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/how-i-use-htmx-with-go" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Not sure how to structure your Go web application? Alex Edwards shares his insights on integrating HTMX to enhance interactivity seamlessly. His approach allows developers to maintain server-side HTML rendering consistency while minimizing JavaScript overhead. The article covers structuring HTML templates, managing partial and full-page responses, and handling redirects with HTMX often used in Go applications. Readers can explore the practical steps involved in setting up a project with HTMX, including file structuring and best practices for embedding assets in Go binaries. This guide is a valuable resource for those looking to build dynamic, user-friendly web applications with Go and HTMX.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.alexedwards.net/blog/how-i-use-htmx-with-go&quot;&gt;Continue reading on &lt;strong&gt;www.alexedwards.net&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/golang&quot;&gt;#golang&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/frontend&quot;&gt;#frontend&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/http&quot;&gt;#http&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/html&quot;&gt;#html&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-08T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/how-i-use-htmx-with-go</id>
    <title>🔗 How I use HTMX with Go</title>
    <updated>2026-08-08T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/the-strangest-hobby-at-the-table" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Handing everyone an LLM subscription might seem sufficient, but it actually limits their potential. A shared, self-hosted agent creates a configured environment tailored to company context, ensures that connected tools are accessible, and maintains clear boundaries. This article argues that companies benefit more from owning this layer rather than renting it. The piece outlines strategic ways for businesses to begin this transition, emphasizing that a self-hosted solution allows for greater customization and adaptability, which are crucial in a competitive landscape. It reassures organizations that starting small is a viable tactic, making it easier to implement significant changes.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://madewithlove.com/blog/the-strangest-hobby-at-the-table/&quot;&gt;Continue reading on &lt;strong&gt;madewithlove.com&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/ai&quot;&gt;#ai&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/devops&quot;&gt;#devops&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-08T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/the-strangest-hobby-at-the-table</id>
    <title>🔗 The strangest hobby at the table</title>
    <updated>2026-08-08T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/nginx-vs-caddy-vs-traefik-in-2026-i-ran-all-three-under-real-production-load" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Same Kubernetes cluster, same microservices, same TLS requirements. One proxy broke during ingress-nginx migration week. Guess which.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://medium.com/@developeryusuf/nginx-vs-caddy-vs-traefik-in-2026-i-ran-all-three-under-real-production-load-64e412f4062b&quot;&gt;Continue reading on &lt;strong&gt;medium.com&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/devops&quot;&gt;#devops&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/testing&quot;&gt;#testing&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/kubernetes&quot;&gt;#kubernetes&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-07T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/nginx-vs-caddy-vs-traefik-in-2026-i-ran-all-three-under-real-production-load</id>
    <title>🔗 Nginx vs Caddy vs Traefik in 2026 — I Ran All Three Under Real Production Load</title>
    <updated>2026-08-07T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/how-to-hire-engineers-for-strong-judgment-and-taste" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Judgment and taste are now critical hiring signals in engineering, as Sage Lazzaro explains. With AI taking over execution, developers must rapidly evaluate outputs and make informed product decisions. Companies are evolving their hiring practices, moving towards open-ended projects and assessing candidate thought processes rather than sheer knowledge. Candidates who struggle to articulate their decision-making raise red flags. Emphasis is placed on curiosity and nuanced thinking, reflecting the need for engineers to balance technical judgment with product sense. For example, roles like Forward Deployed Engineers require deep engagement with customer needs, making thoughtful decision-making more crucial than ever. This article highlights the shift in hiring strategies and the importance of identifying candidates who excel in both judgment and taste.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://leaddev.com/hiring/how-to-hire-engineers-for-strong-judgment-and-taste&quot;&gt;Continue reading on &lt;strong&gt;leaddev.com&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/development&quot;&gt;#development&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/ai&quot;&gt;#ai&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-07T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/how-to-hire-engineers-for-strong-judgment-and-taste</id>
    <title>🔗 How to hire engineers for strong judgment and taste</title>
    <updated>2026-08-07T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/why-pogacar-rides-on-a-car-tire-brand" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Why are pro cyclists like Tadej Pogačar riding on tires made by car manufacturers? Jan Heine reveals the surprising truth behind tire sponsorship in the Tour de France. While companies like Continental dominate road racing sponsorships, it&apos;s primarily car tires being promoted, not bike tires. With costs running into millions, small brands struggle to compete despite offering quality products. Heine highlights that while small makers find success in gravel races, the high stakes of pro cycling often favor larger brands willing to invest heavily. The article provides an insightful look into the financial strategies behind sponsorships in elite road racing, illustrating how marketing priorities can overshadow the sport&apos;s rich cycling heritage.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.renehersecycles.com/why-pogacar-rides-on-a-car-tire-brand/&quot;&gt;Continue reading on &lt;strong&gt;www.renehersecycles.com&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/sports&quot;&gt;#sports&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-07T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/why-pogacar-rides-on-a-car-tire-brand</id>
    <title>🔗 Why Pogačar rides on a car tire brand</title>
    <updated>2026-08-07T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/your-dropbox-is-now-a-skill-server" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;sx 2.0, a new app for Mac, Windows, and Linux, addresses the challenge of sharing AI skills among non-technical teams. By using a shared folder in Dropbox or similar services, teams can easily publish and synchronize their skills without needing git or terminal access. The app translates skills into various AI client formats seamlessly, allowing for effortless integration.&lt;/p&gt;
&lt;p&gt;Moreover, the release includes a pluggable extension system that enables teams to customize their workflows without bloating the core product. With built-in tools to monitor skill usage and ensure content quality, sx 2.0 targets marketing, legal, and sales teams who can now leverage AI without technical barriers through a simple, user-friendly interface. The emphasis on distribution aims to democratize access to AI knowledge across organizations.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://sleuth-io.github.io/sx/2026/07/10/your-dropbox-is-now-a-skill-server.html&quot;&gt;Continue reading on &lt;strong&gt;sleuth-io.github.io&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/tools&quot;&gt;#tools&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/ai&quot;&gt;#ai&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/announcement&quot;&gt;#announcement&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-06T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/your-dropbox-is-now-a-skill-server</id>
    <title>🔗 Your Dropbox is now a skill server</title>
    <updated>2026-08-06T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/kubernetes-dashboard-to-headlamp-a-step-by-step-guide" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Kubernetes Dashboard and Headlamp serve different roles in a cluster. Headlamp connects via &lt;code&gt;kubeconfig&lt;/code&gt;, allowing for desktop or in-cluster usage, while the Kubernetes Dashboard is strictly in-cluster. This article breaks down the processes for migrating from Dashboard to Headlamp. It highlights key differences in user experience, installation methods, and permissions management. A pre-migration checklist ensures a smooth transition, emphasizing the importance of understanding RBAC rules. By suggesting rollout plans, it gives teams structure in their migration approach. Ultimately, Headlamp simplifies managing multiple clusters with its user-friendly interface. It caters to both individual and shared access needs. This guide demystifies what it takes to move from Dashboard to Headlamp, equipping users with the information they need for a successful shift.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://kubernetes.io/blog/2026/07/13/kubernetes-dashboard-to-headlamp/&quot;&gt;Continue reading on &lt;strong&gt;kubernetes.io&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/tools&quot;&gt;#tools&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/devops&quot;&gt;#devops&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/kubernetes&quot;&gt;#kubernetes&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-06T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/kubernetes-dashboard-to-headlamp-a-step-by-step-guide</id>
    <title>🔗 Kubernetes Dashboard to Headlamp: A Step-by-Step Guide</title>
    <updated>2026-08-06T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/markdown-support-coming-in-netnewswire" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;NetNewsWire is about to embrace &lt;code&gt;source:markdown&lt;/code&gt; elements in its next release. This move makes it the first mainstream RSS client to fully support Markdown. The integration allows WordLand-written WordPress posts, which already feature the necessary RSS feeds, to be published and rendered in Markdown. Users can simply log into WordLand and start creating content that will automatically be displayed in NetNewsWire via this format. A GitHub thread has been initiated to address any questions regarding this capability.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://daveverse.org/2025/10/30/markdown-support-coming-in-netnewswire/&quot;&gt;Continue reading on &lt;strong&gt;daveverse.org&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/tools&quot;&gt;#tools&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/announcement&quot;&gt;#announcement&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-06T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/markdown-support-coming-in-netnewswire</id>
    <title>🔗 Markdown support coming in NetNewsWire</title>
    <updated>2026-08-06T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/introducing-mishka-chelekom-v0-0-9" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Mishka Chelekom v0.0.9 revolutionizes how AI agents interact with Phoenix UI. This release adds a built-in MCP server, enabling AI to utilize your components accurately. In addition, it boasts over 35 new headless components that are unstyled yet fully accessible, allowing complete design customization without sacrificing functionality. The new Kit allows users to reuse and restyle components easily without altering original code, preserving project integrity. With a growing community behind it and over 55,000 downloads, this version solidifies Mishka Chelekom&apos;s position as a powerful tool for developers looking to integrate AI effectively into their Phoenix applications.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://mishka.tools/blog/introducing-mishka-chelekom-v0.0.9-ai-native-phoenix-components-with-mcp-headless-ui-and-the-kit&quot;&gt;Continue reading on &lt;strong&gt;mishka.tools&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/ai&quot;&gt;#ai&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/phoenix&quot;&gt;#phoenix&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-05T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/introducing-mishka-chelekom-v0-0-9</id>
    <title>🔗 Introducing Mishka Chelekom v0.0.9</title>
    <updated>2026-08-05T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/kubernetes-architecture" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Kubernetes isn’t just another container orchestration tool; it’s an essential piece of cloud-native architecture that transformed how applications are managed. Neo Kim and Ayaan explain Kubernetes architecture, breaking down its components like the control plane and worker nodes. They illustrate how Kubernetes operates as a distributed system, ensuring applications stay available and resilient even as demands change. The authors emphasize the importance of concepts like desired state versus actual state, highlighting Kubernetes’ ability to self-heal and maintain the system’s equilibrium. This article not only provides a solid foundation for understanding how Kubernetes works but also makes a compelling case for why mastering its architecture is crucial for modern developers and architects.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://newsletter.systemdesign.one/p/kubernetes-architecture&quot;&gt;Continue reading on &lt;strong&gt;newsletter.systemdesign.one&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/development&quot;&gt;#development&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/devops&quot;&gt;#devops&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/kubernetes&quot;&gt;#kubernetes&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-05T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/kubernetes-architecture</id>
    <title>🔗 Kubernetes architecture</title>
    <updated>2026-08-05T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/best-and-worst-software-projects-what-developers-really-think" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;AI significantly accelerates software delivery, but human decision-making remains crucial. Engineers recently discussed the role of AI in their projects, emphasizing its ability to enhance speed without replacing critical thinking and strategic choices. The insights reflect a balanced perspective on technology&apos;s place in development processes, highlighting the importance of creativity and judgment. In a rapidly evolving tech landscape, understanding the boundaries of AI&apos;s capabilities is essential for developers who aim to leverage it effectively while retaining control over their projects.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://shiftmag.dev/developers-are-the-reason-behind-best-and-worst-parts-of-software-development-10670/&quot;&gt;Continue reading on &lt;strong&gt;shiftmag.dev&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/development&quot;&gt;#development&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/ai&quot;&gt;#ai&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-05T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/best-and-worst-software-projects-what-developers-really-think</id>
    <title>🔗 Best and worst software projects: What developers really think</title>
    <updated>2026-08-05T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/prefer-strict-tables-in-sqlite" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Strict tables in SQLite avoid datatype issues by enforcing rigid typing, preventing common mistakes like inserting text into integer columns. By appending &lt;code&gt;STRICT&lt;/code&gt; to a table’s definition, users ensure that type mismatches are not allowed during inserts and updates. In contrast to non-strict tables, which permit any type in any column, strict tables help maintain data integrity and clarity. This article highlights the advantages and limitations of using strict tables, including better validation and avoiding creating columns with invalid types. While strict tables might introduce some performance considerations, the author argues that the benefits in data integrity far outweigh the potential drawbacks. The preference for strict tables is supported by examples and a discussion on SQLite&apos;s flexible typing.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://evanhahn.com/prefer-strict-tables-in-sqlite/&quot;&gt;Continue reading on &lt;strong&gt;evanhahn.com&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/database&quot;&gt;#database&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/sqlite&quot;&gt;#sqlite&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-04T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/prefer-strict-tables-in-sqlite</id>
    <title>🔗 Prefer strict tables in SQLite</title>
    <updated>2026-08-04T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/rewriting-bun-in-rust" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Bun&apos;s evolution from Zig to Rust was not just a coding challenge; it aimed to resolve fundamental stability issues. The article details the ambitious journey of rewriting Bun&apos;s large codebase to enhance memory safety and eliminate bugs inherent in manual memory management. Originally a port from Go to Zig, the developer recognized weaknesses in Zig&apos;s handling of garbage-collected and manually-managed memory. By leveraging a new model from Anthropic, the team performed an efficient mechanical port to Rust, thus enabling safer code practices through Rust&apos;s strong type system and automatic memory management. The result? A more robust Bun, aiming for long-term stability and performance enhancement without sacrificing its original feature set. It&apos;s a case study in planning, execution, and leveraging AI in software development for increased reliability.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://bun.com/blog/bun-in-rust&quot;&gt;Continue reading on &lt;strong&gt;bun.com&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/rust&quot;&gt;#rust&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/development&quot;&gt;#development&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/ai&quot;&gt;#ai&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-04T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/rewriting-bun-in-rust</id>
    <title>🔗 Rewriting Bun in Rust</title>
    <updated>2026-08-04T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/ever-run-into-a-postgresql-query-that-you-can-figure-out-what-it-does" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Ever encountered an indecipherable PostgreSQL query that you still need to support? This article outlines how DBeaver&apos;s AI Assistant can demystify complex queries for users. With DBeaver 26.1.2, the AI Assistant analyzes queries and provides understandable explanations. The author illustrates this tool&apos;s efficacy using a sample query that identifies the top 10 most popular films by rental count and total revenue. From common table expressions (CTEs) to subqueries, the breakdown makes clear how the query&apos;s elements interact to produce results, highlighting the AI&apos;s utility when faced with obfuscated SQL. This guide empowers developers and database administrators to tackle intimidating SQL queries with confidence, showcasing an essential feature for anyone working with PostgreSQL.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://stokerpostgresql.blogspot.com/2026/07/ever-run-into-postgresql-query-that-you.html&quot;&gt;Continue reading on &lt;strong&gt;stokerpostgresql.blogspot.com&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/database&quot;&gt;#database&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/ai&quot;&gt;#ai&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/postgresql&quot;&gt;#postgresql&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/sql&quot;&gt;#sql&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-04T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/ever-run-into-a-postgresql-query-that-you-can-figure-out-what-it-does</id>
    <title>🔗 Ever run into a PostgreSQL query that you can figure out what it does??</title>
    <updated>2026-08-04T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/more-shell-patterns-i-use-weekly" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;This article shares useful Bash patterns and techniques that boost productivity for everyday tasks. The author highlights various methods like using &lt;code&gt;sed&lt;/code&gt; and &lt;code&gt;xargs&lt;/code&gt; for find-and-replace operations, employing &lt;code&gt;while&lt;/code&gt; loops until success, and parallelizing commands with &lt;code&gt;wait&lt;/code&gt;. The discussion emphasizes the importance of clean output and error handling, using temporary directories for logs with &lt;code&gt;mktemp&lt;/code&gt;, and enhancing user legibility with color-coded output. The author also advocates for efficient file manipulation using shell constructs, recommending &lt;code&gt;awk&lt;/code&gt; for filtering data instead of &lt;code&gt;grep&lt;/code&gt;. These patterns, though simple, can significantly streamline workflows, especially for those working with commands regularly.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://will-keleher.com/posts/more-shell-patterns-i-use-weekly/&quot;&gt;Continue reading on &lt;strong&gt;will-keleher.com&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/terminal&quot;&gt;#terminal&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/linux&quot;&gt;#linux&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-03T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/more-shell-patterns-i-use-weekly</id>
    <title>🔗 More shell patterns I use weekly</title>
    <updated>2026-08-03T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/why-backlogs-are-harmful-why-they-never-shrink-and-what-to-do-instead" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Backlogs never shrink, and their existence often leads to unproductive practices. When teams rely on them, they merely accumulate tasks that distract from prioritizing what truly matters. The article points out that important tasks rarely enter the backlog as teams instinctively know what needs immediate attention. This misalignment causes waste and elongates cycle times, as tasks languish unattended. A well-managed product team can avoid the pitfalls of backlogs by employing a high-level roadmap and maintaining close communication with engineers. In practice, this means regularly revisiting goals, effectively filtering bugs, and keeping the focus on immediate tasks. The author argues that instead of allowing unnecessary tasks to clutter workflows, it’s essential to be ruthless in prioritization and decision-making to enhance productivity and strategic alignment.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.lucasfcosta.com/blog/backlogs-are-useless&quot;&gt;Continue reading on &lt;strong&gt;www.lucasfcosta.com&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/development&quot;&gt;#development&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-03T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/why-backlogs-are-harmful-why-they-never-shrink-and-what-to-do-instead</id>
    <title>🔗 Why backlogs are harmful, why they never shrink, and what to do instead</title>
    <updated>2026-08-03T08:00:00Z</updated>
  </entry>
</feed>