<?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">
  <title>🐥 YellowDuck.be</title>
  <id>https://www.yellowduck.be/posts/feed</id>
  <updated>2026-10-22T17:00:00Z</updated>
  <author>
    <name>Pieter Claerhout</name>
    <email>pieter@yellowduck.be</email>
  </author>
  <link rel="self" href="https://www.yellowduck.be/posts/feed"/>
  <link rel="alternate" href="https://www.yellowduck.be"/>
  <entry>
    <id>https://www.yellowduck.be/posts/how-to-build-innovation-teams</id>
    <title>🔗 How to build innovation teams</title>
    <updated>2026-10-22T17:00:00Z</updated>
    <published>2026-10-22T17:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/how-to-build-innovation-teams"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Why do people believe you can build an innovation team by hiring a few smart people and giving them a creative space? Phil McKinney's article challenges this notion, sharing insights from his experience leading innovation teams at HP and CableLabs. He argues that without a strong foundational culture and the right roles, innovation efforts often fail. McKinney outlines six essential steps for building effective innovation teams, emphasizing the importance of recruiting specific roles rather than just talent. He illustrates how processes must be tailored to a company’s unique context rather than blindly adopted from successful examples elsewhere. The piece is not just theoretical; it’s based on practical lessons learned from McKinney’s experiences, including a cautionary tale about the pitfalls of imitating others without adaptation. Readers seeking to cultivate innovation will find valuable strategies and insights here.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.philmckinney.com/how-to-build-innovation-teams-my-playbook-from-hp-and-cablelabs/&quot;&gt;Continue reading on &lt;strong&gt;www.philmckinney.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>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/seven-fujifilm-settings-that-ruin-your-photos</id>
    <title>🔗 Seven Fujifilm settings that ruin your photos</title>
    <updated>2026-10-22T13:00:00Z</updated>
    <published>2026-10-22T13:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/seven-fujifilm-settings-that-ruin-your-photos"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Fujifilm cameras often come with default settings that can hinder photo quality, like Auto ISO and electronic shutter defaults, leading to issues such as blurry low-light images and incorrect white balance. Chris Lee from pal2tech points out seven common mistakes made by Fujifilm users, including the problem of custom settings potentially overwriting themselves and SD card configuration errors that prevent real-time backups. He emphasizes the importance of revisiting and adjusting factory settings to meet specific photography needs, suggesting that these tailored tweaks can significantly improve shooting outcomes. Lee provides insights on how these settings operate within the Fujifilm X-S20 and X-T5, advocating for a thoughtful approach to camera configuration rather than relying on presets, which are often designed for casual use.&lt;/p&gt;
&lt;p&gt;Watch the video linked for specific adjustments and in-depth corrections on these issues.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://fstoppers.com/education/seven-fujifilm-settings-should-check-carefully-904652&quot;&gt;Continue reading on &lt;strong&gt;fstoppers.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;/p&gt;</content>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/evolving-programming-languages-in-the-ai-era</id>
    <title>🔗 Evolving programming languages in the AI era</title>
    <updated>2026-10-22T08:00:00Z</updated>
    <published>2026-10-22T08:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/evolving-programming-languages-in-the-ai-era"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;How will programming languages evolve as coding agents begin to dominate the coding landscape? José Valim argues that this shift will require a reevaluation of communities, ecosystems, and programming language design.  The article is divided into two parts: Reflections and Agentic Tooling. In his reflections, Valim questions the impact of agents on programming communities and their frameworks, noting that agent-driven coding could diminish collaborative efforts. He highlights the need for languages to enhance guarantees while considering ergonomics for agents. Meanwhile, the section on Agentic tooling proposes innovative approaches to programming, emphasizing stronger user constraints and runtime observability over traditional debuggers. This thought-provoking piece suggests that as coding agents take the helm, the industry must adapt to new paradigms of programming, ensuring tools remain effective and purposeful.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://dashbit.co/blog/evolving-ai-era&quot;&gt;Continue reading on &lt;strong&gt;dashbit.co&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/ai&quot;&gt;#ai&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/elixir&quot;&gt;#elixir&lt;/a&gt;&lt;/p&gt;</content>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/background-jobs-with-oban-part-1-stop-blocking-your-liveview</id>
    <title>🔗 Background jobs with Oban, part 1: stop blocking your LiveView</title>
    <updated>2026-10-21T17:00:00Z</updated>
    <published>2026-10-21T17:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/background-jobs-with-oban-part-1-stop-blocking-your-liveview"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;A slow HTTP fetch can freeze your LiveView, impacting user experience. This article illustrates how to offload this slow job using Oban, a job processing library for Elixir. The piece guides readers through integrating Oban into a Phoenix application by setting up a jobs table, configuring queues, and writing a worker to handle tasks in the background. By transitioning slow processes out of the LiveView event handler, the app becomes more responsive, allowing users to interact without delays when processing links. The author provides a thorough code walkthrough, ensuring that developers can follow along with their own implementations. This approach optimizes performance and enhances user satisfaction by minimizing wait times during web page fetching.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://potions.io/blog/background-jobs-with-oban-part-1&quot;&gt;Continue reading on &lt;strong&gt;potions.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/elixir&quot;&gt;#elixir&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/phoenix&quot;&gt;#phoenix&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;/p&gt;</content>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/when-a-pull-request-balloons-extract</id>
    <title>🔗 When a pull request balloons, extract</title>
    <updated>2026-10-21T13:00:00Z</updated>
    <published>2026-10-21T13:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/when-a-pull-request-balloons-extract"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;A Pull Request should never exceed 3,000 lines. Mike Zornek highlights his challenges with a feature for arbitrary refunds on an order. After successfully merging the first two phases of his implementation, Zornek faced overwhelming complexity with the UI in phase three, causing his Pull Request to balloon. Rather than merging a massive PR that risks getting missed during review, he extracted smaller components into manageable PRs. He pulled out unrelated bug fixes and additional test coverage to simplify the review process. This approach allows for clearer feedback and greater confidence when deploying code, especially for features that are critical for handling financial transactions. Extracting improvements from a large PR can be time-consuming but ultimately pays off in quality and maintainability.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://mikezornek.com/posts/2026/9/when-a-pull-request-balloons-extract/&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/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;a href=&quot;https://www.yellowduck.be/tags/git&quot;&gt;#git&lt;/a&gt;&lt;/p&gt;</content>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/rip-commercial-ocr-an-open-source-model-just-topped-every-benchmark</id>
    <title>🔗 RIP commercial OCR. An open-source model just topped every benchmark.</title>
    <updated>2026-10-21T08:00:00Z</updated>
    <published>2026-10-21T08:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/rip-commercial-ocr-an-open-source-model-just-topped-every-benchmark"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Chandra OCR 2, a model from Brooklyn's Datalab, recently made waves in the OCR realm. With just 4 billion parameters, it outperformed both GPT-4o and Gemini across 90 languages, showcasing a remarkable ability to decode complex layouts and produce structured formats like Markdown and HTML. In independent benchmarks, it scored a staggering 85.9%, highlighting a clear edge over well-known models, diverging from typical OCR tools that struggle with intricacies like handwritten notes or multi-column documents. The article by Sumit Pandey emphasizes the implications of Chandra's performance, suggesting it could reframe expectations in document processing pipelines and beyond. The model’s open-source nature and easy accessibility, paired with its remarkable accuracy, means it’s poised to be a game-changer for anyone working with tricky, real-world documents.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://freedium-mirror.cfd/https%3A%2F%2Fwww.towardsdeeplearning.com%2Frip-commercial-ocr-an-open-source-model-just-topped-every-benchmark-351bf9d6be10&quot;&gt;Continue reading on &lt;strong&gt;freedium-mirror.cfd&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/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>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/what-is-the-difference-between-a-cto-and-a-vp-or-head-of-engineering</id>
    <title>🔗 What is the difference between a CTO and a VP or Head of Engineering?</title>
    <updated>2026-10-20T13:00:00Z</updated>
    <published>2026-10-20T13:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/what-is-the-difference-between-a-cto-and-a-vp-or-head-of-engineering"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;What distinguishes a CTO from a VP or Head of Engineering? This article clarifies their unique roles and responsibilities. A CTO focuses on enabling diverse technological outcomes, resembling a visionary strategist, while the VP or Head of Engineering is tasked with executing the current business strategy, maintaining a strong emphasis on product delivery. The piece underscores the importance of striking a balance between short- and long-term goals, showcasing examples from companies like Amazon and Microsoft. It argues that while titles may seem less significant in smaller organizations, they hold value for external recognition and relationships, particularly as careers evolve. Insightful reflections from the author highlight the dynamic nature of these roles and the impact of titles on professional journeys.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://code.dblock.org/2015/05/07/what-is-the-difference-between-cto-and-vp-or-head-of-engineering.html&quot;&gt;Continue reading on &lt;strong&gt;code.dblock.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/development&quot;&gt;#development&lt;/a&gt;&lt;/p&gt;</content>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/postgres-at-time-zone-utc-does-not-do-what-you-think-it-does</id>
    <title>🔗 Postgres AT TIME ZONE 'UTC' does not do what you think it does</title>
    <updated>2026-10-20T08:00:00Z</updated>
    <published>2026-10-20T08:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/postgres-at-time-zone-utc-does-not-do-what-you-think-it-does"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;The &lt;code&gt;AT TIME ZONE 'UTC'&lt;/code&gt; in Postgres may mislead developers into thinking it uniformly converts all timestamps to UTC, but this is not the case. Timestamps without time zones are converted directly to UTC, but timestamps with time zones are treated differently. Specifically, Postgres only adjusts their display according to the specified time zone rather than altering their actual values. This subtlety can lead to confusion in applications that handle time-sensitive data. Understanding this behavior is crucial for accurate time data manipulation in Postgres. Misinterpreting the conversion can result in significant issues in data reporting and analytics. Developers are advised to approach time zone conversions with care and ensure they grasp the nuances of time handling in Postgres, especially in complex systems that rely on accurate time tracking.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://bookofrevenue.com/blog/6ab81e9a97a13f0001f7e4e1/postgres-at-time-zone-u-does-not-do-what-you-think-it-does&quot;&gt;Continue reading on &lt;strong&gt;bookofrevenue.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/postgresql&quot;&gt;#postgresql&lt;/a&gt;&lt;/p&gt;</content>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/why-you-should-work-out-loud</id>
    <title>🔗 Why you should work out loud</title>
    <updated>2026-10-19T17:00:00Z</updated>
    <published>2026-10-19T17:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/why-you-should-work-out-loud"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;This article highlights the importance of documenting one's work instead of simply inventing content. It emphasizes that AI can assist in content creation, but it cannot replicate the depth of experiences accumulated over years. The author shares insights from Allen Buchanan, pointing out that the most compelling content often stems from lived experiences rather than imagination. The piece encourages creating a digital record of expertise, noting that with AI's capabilities to search and organize this knowledge, its value increases significantly over time. Steve Mays reflects on how his blog became a platform for capturing his professional journey, reminding readers of the power of shared experiences.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.smays.com/2026/09/work-out-loud/&quot;&gt;Continue reading on &lt;strong&gt;www.smays.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>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/measuring-ais-impact-on-delivery-speed</id>
    <title>🔗 Measuring AI’s impact on delivery speed</title>
    <updated>2026-10-19T13:00:00Z</updated>
    <published>2026-10-19T13:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/measuring-ais-impact-on-delivery-speed"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Is AI making software development faster? James Shore dives deep into quantifying this impact on delivery speed in his latest article. He emphasizes that while many believe productivity will rise with AI, the true measure lies in value produced relative to money spent. Delivery speed is merely a fraction of overall productivity, and distinguishing it from mere output is crucial. Shore outlines a rigorous approach to measurement that involves randomized controlled trials to retain accuracy amidst varied estimates and individual work styles. By doing so, he highlights the necessity of understanding what investments in AI truly yield for development teams, cautioning against superficial metrics. This insightful piece continues his series on AI's role in software development, paving the way for future discussions on unintended consequences and overall business outcomes.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.jamesshore.com/v2/blog/2026/measuring-ais-impact-on-delivery-speed&quot;&gt;Continue reading on &lt;strong&gt;www.jamesshore.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>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/what-i-believe-about-the-future-of-software-development</id>
    <title>🔗 What I believe about the future of software development</title>
    <updated>2026-10-19T08:00:00Z</updated>
    <published>2026-10-19T08:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/what-i-believe-about-the-future-of-software-development"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;What will the future hold for software development? Thorsten Ball boldly claims that the era of code review is already over, suggesting that humans will no longer find bugs in code generated by AI models. Instead, the focus will shift to reviewing system architecture. He anticipates the decline of unit tests, arguing that if models can produce flawless code, there's no need for safety checks. He also discusses how the traditional craft of coding may fade, making way for software that solves business problems more effectively. As we enter this post-binary era, the value of performance optimization will diminish. Tokens will redefine developer tools, making command line interfaces obsolete. Ball predicts that the roles within software development teams will dissolve, and economic access to software production will shift, leading to profound changes in the industry. This thought-provoking piece pushes readers to consider the future landscape of technology.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://thorstenball.com/blog/2026/09/19/what-i-believe-about-the-future-of-software-development/&quot;&gt;Continue reading on &lt;strong&gt;thorstenball.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>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/clean-code-is-not-the-same-as-clear-code-comments-were-never-the-problem</id>
    <title>🔗 Clean code is not the same as clear code: comments were never the problem</title>
    <updated>2026-10-18T13:00:00Z</updated>
    <published>2026-10-18T13:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/clean-code-is-not-the-same-as-clear-code-comments-were-never-the-problem"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Why does clean code sometimes leave developers puzzled? In a thought-provoking article, Giorgi Kobaidze argues that comments are essential for understanding complex logic in code. He draws a parallel between road signs and code, emphasizing that even well-structured code can benefit from clarifications. Kobaidze addresses common misconceptions about comments, stating they aren't a sign of weakness but a helpful guide. Good comments translate dense code, explain decisions, and prevent confusion for other developers. He warns against relying solely on commit messages for explanations, noting how easily important information can be lost over time. The piece concludes with advice on how to comment effectively, highlighting the fine line between useful annotations and clutter.&lt;/p&gt;
&lt;p&gt;Overall, the article provides invaluable insights for developers looking to enhance code readability and maintainability without sacrificing the clarity that comments can bring.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://dev.to/georgekobaidze/clean-code-is-not-the-same-as-clear-code-comments-were-never-the-problem-42n?via=dailydev&quot;&gt;Continue reading on &lt;strong&gt;dev.to&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>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/virtual-environments-in-python</id>
    <title>🔗 Virtual environments in Python</title>
    <updated>2026-10-18T08:00:00Z</updated>
    <published>2026-10-18T08:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/virtual-environments-in-python"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Virtual environments are essential for managing Python projects effectively. The recommended tool is &lt;code&gt;uv&lt;/code&gt;, which not only manages project dependencies but also creates isolated environments. This article details how to use &lt;code&gt;uv&lt;/code&gt; to initialize projects, add packages, and automate virtual environment management. Operating outside of &lt;code&gt;uv&lt;/code&gt; usually means diving into the lower-level workings of virtual environments. It explains creating, activating, and deactivating environments along with checking their status. Readers get practical commands and examples to manage packages, including the usage of &lt;code&gt;pyproject.toml&lt;/code&gt; and &lt;code&gt;requirements.txt&lt;/code&gt;. The guide emphasizes the importance of isolation and package management to avoid conflicts in project dependencies. Simply put, understanding these concepts allows developers to maintain clean and organized Python environments for their projects.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://tiangolo.com/guides/virtual-environments/&quot;&gt;Continue reading on &lt;strong&gt;tiangolo.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;/p&gt;</content>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/testing-async-python-without-losing-your-mind</id>
    <title>🔗 Testing async Python without losing your mind</title>
    <updated>2026-10-17T17:00:00Z</updated>
    <published>2026-10-17T17:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/testing-async-python-without-losing-your-mind"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Async testing in Python can be challenging, yet it's not as daunting when you understand key concepts. The article by Peyton Green dives into common pitfalls like event loop scope mismatches and intricate fixture lifecycle issues that often lead to confusion during testing. With detailed examples, it discusses the critical differences between using &lt;code&gt;pytest-asyncio&lt;/code&gt; and &lt;code&gt;anyio&lt;/code&gt;, showing how to set up async tests properly and avoid frequent errors. Green emphasizes the importance of matching fixture scopes with event loops to ensure smooth operation. This guide not only highlights these common errors but also provides concrete solutions, making async testing approachable even for those new to the framework. Ultimately, readers gain a clear understanding of testing async code through insightful strategies for FastAPI endpoints and handling background tasks effectively, all aimed at streamlining the testing process.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://dev.to/peytongreen_dev/testing-async-python-without-losing-your-mind-5344&quot;&gt;Continue reading on &lt;strong&gt;dev.to&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/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>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/natural-sorting-in-postgresql-mastering-custom-collations</id>
    <title>🔗 Natural sorting in PostgreSQL: mastering custom collations</title>
    <updated>2026-10-17T13:00:00Z</updated>
    <published>2026-10-17T13:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/natural-sorting-in-postgresql-mastering-custom-collations"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Sorting alphanumeric data usually follows character code points, which can lead to confusing results for numbers. This article reveals how to implement &amp;quot;natural&amp;quot; sorting in Postgres, allowing numbers to be sorted by value rather than code point. It explains creating custom collation objects using the &lt;code&gt;CREATE COLLATION&lt;/code&gt; command, focusing on useful examples for numeric ordering. The author clarifies that collations determine the sort order of characters, specifically beneficial when handling alphanumeric strings. With insights about the ICU provider and locale definitions, this guide offers important context for when developers need to sort mixed data types effectively. The hands-on approach culminates in applying the collation to enhance the sorting syntax, making Postgres a powerful tool in better organizing data.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://testdouble.com/insights/natural-sorting-postgres-collation&quot;&gt;Continue reading on &lt;strong&gt;testdouble.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/postgresql&quot;&gt;#postgresql&lt;/a&gt;&lt;/p&gt;</content>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/python-3-15-preview-lazy-imports</id>
    <title>🔗 Python 3.15 Preview: Lazy Imports</title>
    <updated>2026-10-17T08:00:00Z</updated>
    <published>2026-10-17T08:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/python-3-15-preview-lazy-imports"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Python 3.15 adds lazy imports: a lazy keyword that puts off loading a module until the first time you use it. The import statement stays where it belongs, at the top of your file, but the work of running it moves to the moment something touches the module’s name. In this tutorial, you’ll make a command-line tool start more than twice as fast without moving a single import.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://realpython.com/python315-lazy-imports/&quot;&gt;Continue reading on &lt;strong&gt;realpython.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;/p&gt;</content>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/python-3-15-is-bigger-than-you-think-7-new-features-worth-using-in-2026</id>
    <title>🔗 Python 3.15 is bigger than you think: 7 new features worth using in 2026</title>
    <updated>2026-10-16T17:00:00Z</updated>
    <published>2026-10-16T17:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/python-3-15-is-bigger-than-you-think-7-new-features-worth-using-in-2026"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Python 3.15 brings significant enhancements beyond typical library improvements. It introduces important features like &lt;code&gt;lazy import&lt;/code&gt;, which allows deferring module loading until needed, and the &lt;code&gt;frozendict&lt;/code&gt;, providing a new immutable mapping type. The &lt;code&gt;sentinel()&lt;/code&gt; function replaces the &lt;code&gt;_MISSING&lt;/code&gt; trick for optional values, helping to clarify function parameters. Comprehensions can now directly unpack iterables, simplifying data processing tasks. These features not only simplify code but also enhance performance, making them valuable for developers looking to future-proof their Python projects. With the release still in prerelease, now is an ideal time to explore these updates without affecting production systems. Expect improved readability and maintainability, catering to modern Python practices and enhancing overall coding efficiency.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://freedium-mirror.cfd/https://captain-solaris.medium.com/python-3-15-is-bigger-than-you-think-7-new-features-worth-using-in-2026-0235523fbc03&quot;&gt;Continue reading on &lt;strong&gt;freedium-mirror.cfd&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;/p&gt;</content>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/how-to-fix-nonetype-object-has-no-attribute-errors-without-guessing</id>
    <title>🔗 How to fix 'NoneType' object has no attribute errors (without guessing)</title>
    <updated>2026-10-16T13:00:00Z</updated>
    <published>2026-10-16T13:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/how-to-fix-nonetype-object-has-no-attribute-errors-without-guessing"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;This article unpacks the confusion surrounding the common Python error: &lt;code&gt;AttributeError: 'NoneType' object has no attribute 'name'&lt;/code&gt;. It clarifies that the error is not indicative of a flawed program, but a clear signal that a variable is &lt;code&gt;None&lt;/code&gt; when it shouldn’t be. By following a structured debugging process, readers learn that fixing the problem involves identifying where the &lt;code&gt;None&lt;/code&gt; value originated, confirming its state, and determining appropriate handling for potentially missing data. This approach helps developers avoid superficial fixes that merely address the symptom rather than the root cause. Understanding this process equips programmers with the confidence to tackle similar issues effectively in their own code.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://systemcraftpress.com/blog/nonetype-has-no-attribute/&quot;&gt;Continue reading on &lt;strong&gt;systemcraftpress.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;/p&gt;</content>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/where-rss-is-quietly-heading-decentralization-ai-and-the-return-of-owning-your-feed</id>
    <title>🔗 Where RSS is quietly heading — decentralization, AI, and the return of owning your feed</title>
    <updated>2026-10-16T08:00:00Z</updated>
    <published>2026-10-16T08:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/where-rss-is-quietly-heading-decentralization-ai-and-the-return-of-owning-your-feed"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;RSS has long been a niche tool, favored by tech-savvy users but alienating to everyday people. The article highlights the evolving landscape where two factions are emerging: one yearns for decentralization and control over their feeds, while the other craves modern features that enhance usability. Recent advancements in AI are bridging this gap, enabling apps that transform RSS by eliminating technical complexities. Users can now access their sources easily, benefiting from features like audio summaries and smart organization without losing ownership of their content. As technology advances, RSS is becoming more accessible to a wider audience, positioning itself uniquely where decentralization meets enhanced functionality.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://safeandinformed.com/blog/where-rss-is-quietly-heading&quot;&gt;Continue reading on &lt;strong&gt;safeandinformed.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/ai&quot;&gt;#ai&lt;/a&gt;&lt;/p&gt;</content>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/rss-doesnt-have-to-be-boring</id>
    <title>🔗 RSS doesn’t have to be boring</title>
    <updated>2026-10-15T17:00:00Z</updated>
    <published>2026-10-15T17:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/rss-doesnt-have-to-be-boring"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Ever thought of revamping your RSS feed experience? The article details a makeover done at new.bitecode.dev, enhancing how users subscribe to content. The author explains how traditional RSS feeds often fall short, especially when relying on platforms like Substack, which focus only on the basics. By implementing a custom solution with Django, the site now allows users to filter which articles or notes they want to follow, transforming the passive reading experience into a tailored one. The author emphasizes that RSS is flexible and can empower users to pull exactly what they want, debunking the myth that it’s outdated or boring. The article invites technical enthusiasts to explore these enhancements and realize the potential of RSS feeds in a modern context, even hinting at distinctive applications like personalized content delivery and bot integrations.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.bitecode.dev/p/rss-doesnt-have-to-be-boring&quot;&gt;Continue reading on &lt;strong&gt;www.bitecode.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/frontend&quot;&gt;#frontend&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/django&quot;&gt;#django&lt;/a&gt;&lt;/p&gt;</content>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/ruff-mypy-pytest-and-then-what</id>
    <title>🔗 Ruff, MyPy, pytest, and then what?</title>
    <updated>2026-10-15T13:00:00Z</updated>
    <published>2026-10-15T13:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/ruff-mypy-pytest-and-then-what"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Structural quality in AI-written Python code is often overlooked. The article reveals how tools like Ruff, mypy, and pytest don’t catch issues like code duplication, which can frustrate agents during development. Agents sometimes mirror code across multiple functions and modules without realizing it, leading to confusion and inefficiency. By running structural analyses on a repository and leveraging tools like pyscn, the author shows the impact of code complexity and duplication over time. A few strategic changes can mitigate these issues for better collaboration between human developers and AI. Clear rules for function imports and tracking average complexity are essential for maintaining a clean codebase. Understanding and addressing these pitfalls can enhance the overall structure and readability of Python projects, benefiting both human and AI developers alike.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://codescan.dev/blog/ruff-mypy-pytest-and-then-what&quot;&gt;Continue reading on &lt;strong&gt;codescan.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/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>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/finding-your-broken-glass-a-flaky-test-prompt-for-github-actions</id>
    <title>🔗 Finding your broken glass: A flaky test prompt for GitHub Actions</title>
    <updated>2026-10-15T08:00:00Z</updated>
    <published>2026-10-15T08:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/finding-your-broken-glass-a-flaky-test-prompt-for-github-actions"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Test flakes can wreak havoc on CI processes, costing teams not just time but also developer morale. Mike Zornek highlights the importance of addressing flaky tests in GitHub Actions workflows. By analyzing test failures, teams can quantify the negative impact and uncover root causes, leading to more robust development practices. Zornek provides a practical prompt for using AI tools to identify flaky tests and suggests how to improve the situation. Understanding the cost of these inefficiencies is key to maintaining a happy and productive development environment.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://mikezornek.com/posts/2026/9/finding-flaky-tests/&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/ai&quot;&gt;#ai&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/github&quot;&gt;#github&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/testing&quot;&gt;#testing&lt;/a&gt;&lt;/p&gt;</content>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/the-blog-was-the-retrieval-layer-all-along</id>
    <title>🔗 The blog was the retrieval layer all along</title>
    <updated>2026-10-14T13:00:00Z</updated>
    <published>2026-10-14T13:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/the-blog-was-the-retrieval-layer-all-along"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;This article by Kin Lane reveals an intriguing perspective on how blogging serves as a retrieval system rather than mere content creation. Through a conversation with Emma Kriskinans of Tyk, Lane uncovers her method of documenting not just what she built but also the thought processes behind it. He reflects on his own experience with API Evangelist, arguing that his extensive archive is not just a memory aid but a meticulously maintained record of reasoning over time. As AI technologies evolve, Lane emphasizes the importance of having structured documentation—something he has maintained for years. He advises writers to document their thought processes in a way that allows for future insights, underscoring that the value lies in how we frame our own reasoning rather than just the conclusions we reach. This habit turns into an asset over time, proving beneficial to current and future readers alike.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;http://apievangelist.com/2026/09/04/the-blog-was-the-retrieval-layer-all-along/&quot;&gt;Continue reading on &lt;strong&gt;apievangelist.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;/p&gt;</content>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/continuous-development-with-claude-code-on-github</id>
    <title>🔗 Continuous development with Claude Code on GitHub</title>
    <updated>2026-10-14T08:00:00Z</updated>
    <published>2026-10-14T08:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/continuous-development-with-claude-code-on-github"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;In this article, Piotr Minkowski explains how to leverage the Claude GitHub App for continuous development. By using Claude Code, developers can automatically implement features and review pull requests in response to GitHub issues. The setup involves installing the Claude GitHub App and configuring related GitHub workflows that react to comments in issues or pull requests. A sample project utilizing Spring Boot REST API serves as a demonstration, showcasing effective patterns like JPA persistence and CI pipelines. The workflow is entirely automated, emphasizing minimal developer intervention while ensuring smart code management through AI sufficiency. This innovative approach bridges the gap between issue tracking and code quality, making it a noteworthy method for modern development processes.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://piotrminkowski.com/2026/07/02/continuous-development-with-claude-code-on-github/&quot;&gt;Continue reading on &lt;strong&gt;piotrminkowski.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/ai&quot;&gt;#ai&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/github&quot;&gt;#github&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/java&quot;&gt;#java&lt;/a&gt;&lt;/p&gt;</content>
  </entry>
  <entry>
    <id>https://www.yellowduck.be/posts/homebrew-7-0-0</id>
    <title>🔗 Homebrew: 7.0.0</title>
    <updated>2026-10-13T17:00:00Z</updated>
    <published>2026-10-13T17:00:00Z</published>
    <author><name>Pieter Claerhout</name><email>pieter@yellowduck.be</email></author>
    <link rel="alternate" href="https://www.yellowduck.be/posts/homebrew-7-0-0"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;The newly released Homebrew 7.0.0 introduces significant performance enhancements, making installations and upgrades faster than ever. With improved concurrency during downloads and installations, users can expect reduced wait times and better preparation of packages. The update also brings stronger security measures, including a native macOS app, built-in vulnerability checks, and advisory databases to further reinforce application safety. Notably, support for macOS 10.15 has been dropped, with Intel Macs moving to Tier 3 status. For developers relying on Homebrew, the new features streamline the installation and management processes, emphasizing both speed and security. The article outlines these crucial upgrades and what they mean for users across macOS and Linux platforms.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://brew.sh/2026/09/13/homebrew-7.0.0/&quot;&gt;Continue reading on &lt;strong&gt;brew.sh&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/devops&quot;&gt;#devops&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/announcement&quot;&gt;#announcement&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/mac&quot;&gt;#mac&lt;/a&gt;&lt;/p&gt;</content>
  </entry>
</feed>
