<?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-10-02T17:00:00Z</updated>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/is-agentic-ai-just-automation" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Why are most agents merely flowcharts in disguise? In this insightful piece, Prashant Mudgal critiques the common misconception that agentic AI offers capabilities beyond advanced automation. He delineates a clear distinction: automation handles known unknowns, while agentic AI tackles unknown unknowns. Mudgal presents real-world scenarios, such as aviation maintenance and due diligence, to illustrate how true agentic AI can uncover unprecedented insights, unlike traditional automated systems. He warns organizations that their overly structured processes often suffocate the potential for genuine decision-making. Instead of beginning with predefined use cases, he suggests starting from exceptions observed in workflows. This article is not just theoretical; it is a call to look beyond flowcharts and embrace the chaos where real intelligence can thrive.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://towardsdatascience.com/is-agentic-ai-just-automation/&quot;&gt;Continue reading on &lt;strong&gt;towardsdatascience.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-10-02T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/is-agentic-ai-just-automation</id>
    <title>🔗 Is agentic AI just automation?</title>
    <updated>2026-10-02T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/websockets-vs-sse-should-be-about-ordering-and-correctness" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;When considering WebSockets and Server-Sent Events (SSE), event ordering and correctness are critical for user experience. For instance, a scenario might arise where user actions like adding or removing tags can lead to chaotic and misleading outcomes if events arrive out of order. The author emphasizes that while many advocate for SSE due to perceived simplicity, the real battle lies in ensuring correct event delivery, which can be better handled by WebSockets. WebSockets allow for bidirectional communication, preventing issues that plague SSE and Fetch interactions, where multiple streams could race against each other. The article concludes by asserting that regardless of the technology choice, the essential question remains: how to ensure events are processed in the correct order to avoid confusing users?&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://dashbit.co/blog/websockets-vs-sse&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/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;/p&gt;</content>
    <published>2026-10-02T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/websockets-vs-sse-should-be-about-ordering-and-correctness</id>
    <title>🔗 WebSockets vs. SSE should be about ordering and correctness</title>
    <updated>2026-10-02T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/balancing-flex-items-with-flex-wrap-balance" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;When flexbox items wrap but result in an orphan item, designers often resort to media queries to fix layout issues. However, this can lead to a fragile design that breaks easily with content changes. With the introduction of &lt;code&gt;flex-wrap: balance&lt;/code&gt; in Chrome 150, layouts can appear much more organized. This article provides various solutions to keep flex items balanced, especially in scenarios where they might break into orphan items. Solutions range from using container queries to applying &lt;code&gt;flex-line-count&lt;/code&gt;, showcasing the versatility of modern CSS. Each technique addresses responsive design issues without relying solely on problematic media queries. The ease of using &lt;code&gt;flex-wrap: balance&lt;/code&gt; can dramatically improve the aesthetics and functionality of web layouts, making it an exciting addition to a web designer&apos;s toolkit.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://ishadeed.com/article/flex-wrap-balance/&quot;&gt;Continue reading on &lt;strong&gt;ishadeed.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/frontend&quot;&gt;#frontend&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/css&quot;&gt;#css&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-10-02T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/balancing-flex-items-with-flex-wrap-balance</id>
    <title>🔗 Balancing flex items with flex-wrap: balance</title>
    <updated>2026-10-02T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/my-html-boilerplate-in-2026" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;What does an updated HTML boilerplate look like in 2026? Manuel Matuzović shares his revised foundation for HTML documents, detailing every crucial element along with its purpose. He emphasizes the importance of a correct &lt;code&gt;&lt;!DOCTYPE html&gt;&lt;/code&gt; declaration, character encoding with &lt;code&gt;&lt;meta charset=&quot;UTF-8&quot;&gt;&lt;/code&gt;, and the significance of the &lt;code&gt;lang&lt;/code&gt; attribute in ensuring accessibility. With JavaScript support growing, he also discusses using a &lt;code&gt;no-js&lt;/code&gt; class to handle non-JS environments. The article covers essential features like viewport settings for responsive design and the growing necessity of &lt;code&gt;manifest&lt;/code&gt; files for Progressive Web Applications (PWAs). With an eye on performance and SEO, Matuzović provides a detailed look at the modern expectations of an HTML structure, ensuring it remains efficient and user-friendly. For anyone looking to modernize their HTML approach, this article is a valuable resource for best practices and considerations in 2026.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.matuzo.at/blog/2026/html-boilerplate&quot;&gt;Continue reading on &lt;strong&gt;www.matuzo.at&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/best-practice&quot;&gt;#best-practice&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-10-01T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/my-html-boilerplate-in-2026</id>
    <title>🔗 My HTML boilerplate in 2026</title>
    <updated>2026-10-01T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/build-htop-for-the-web-with-go-datastar" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;How does a backend-driven UI sound? Alex Pliutau showcases how to create an interactive web application using Go and Datastar, focusing on applications where state management occurs entirely on the backend. With Datastar’s hypermedia-first approach, developers can build applications like a monitoring dashboard for host metrics without the need for a complex frontend framework. By leveraging Server-Sent Events (SSE) for updates, it provides a streamlined way to push HTML patches directly from the server to the client. This enables real-time updates with minimal client-side logic. Pliutau dives into practical code examples, including the use of the &lt;code&gt;gopsutil&lt;/code&gt; library for resource metrics, demonstrating how to efficiently implement this framework. It&apos;s a compelling alternative to traditional frontend frameworks for specific use cases.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://packagemain.tech/p/golang-datastar&quot;&gt;Continue reading on &lt;strong&gt;packagemain.tech&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/http&quot;&gt;#http&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-10-01T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/build-htop-for-the-web-with-go-datastar</id>
    <title>🔗 Build htop for the web with Go + Datastar</title>
    <updated>2026-10-01T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/anthropics-claude-now-has-a-browser-of-its-own" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Anthropic has unveiled that its AI assistant, Claude, now includes a built-in browser feature. This addition aims to enhance the assistant&apos;s capabilities by allowing it to access real-time information from the web. As AI integrates deeper into daily tasks, having a browsing capability could bridge the gap between static responses and dynamic data retrieval. The model can now provide more accurate, up-to-date answers, making it a more powerful tool for users. The development reflects a growing trend in AI where tools are being equipped with functionalities that extend beyond traditional limits. Will this feature redefine how users interact with AI? Only time will tell.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://thenewstack.io/claude-built-in-browser-cowork/&quot;&gt;Continue reading on &lt;strong&gt;thenewstack.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/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-10-01T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/anthropics-claude-now-has-a-browser-of-its-own</id>
    <title>🔗 Anthropic&apos;s Claude now has a browser of its own</title>
    <updated>2026-10-01T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/speeding-up-a-phoenix-liveview-web-app-with-a-cdn" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Using a CDN can significantly enhance the performance of Phoenix LiveView web applications, especially those with dynamic content and user sessions. The article outlines an effective way to leverage &lt;code&gt;bunny.net&lt;/code&gt; as a CDN, detailing a low-effort configuration that can lead to high rewards. It emphasizes caching strategies through &lt;code&gt;Plug.Static&lt;/code&gt; and shows how to configure static asset serving from a CDN domain. By adjusting the &lt;code&gt;static_url&lt;/code&gt; in your application&apos;s config and ensuring that asset links use the &lt;code&gt;url&lt;/code&gt; helper, all your static files can efficiently be served from a designated CDN subdomain. Additionally, the article touches on the importance of optimizing outgoing traffic and page load speeds, making it a valuable resource for developers looking to improve their Phoenix LiveView applications with minimal overhead.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://jola.dev/posts/speeding-up-phoenix-liveview-cdn&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/frontend&quot;&gt;#frontend&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;/p&gt;</content>
    <published>2026-09-30T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/speeding-up-a-phoenix-liveview-web-app-with-a-cdn</id>
    <title>🔗 Speeding up a Phoenix LiveView web app with a CDN</title>
    <updated>2026-09-30T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/ducklabs-to-join-aws-projects-to-remain-open-source" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;DuckLabs has announced its upcoming partnership with Amazon Web Services (AWS), set to take effect in early September. This union is aimed at leveraging AWS’s resources and reach, while ensuring that the open-source initiatives underpinning DuckDB, DuckLake, and Quack remain available under the MIT license. The DuckDB Foundation will continue to oversee these projects, preserving the spirit of community contribution.&lt;/p&gt;
&lt;p&gt;With over one million downloads daily, DuckDB has proven to be a crucial tool for developers worldwide. The move to join AWS is seen as a necessary step to scale the technology further, enabling DuckLabs to focus on technical advancements without compromising on the open-source ethos that fueled its success. This collaboration promises even greater opportunities for both the technology and its global community of users, contributors, and advocates as they enter this new chapter together.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://ducklabs.com/news/2026/08/26/ducklabs-to-join-aws&quot;&gt;Continue reading on &lt;strong&gt;ducklabs.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/devops&quot;&gt;#devops&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-09-30T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/ducklabs-to-join-aws-projects-to-remain-open-source</id>
    <title>🔗 DuckLabs to join AWS, projects to remain open source</title>
    <updated>2026-09-30T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/the-dutch-community-where-people-live-on-strips-of-land-in-a-lake" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;In the Dutch town of Loosdrecht, residents inhabit homes perched on slim islands within a lake. This distinctive living arrangement originated from peat mining that created narrow strips of land meant for drying peat. Though it remained a quirky geographical feature for years, the 20th century saw developers transform these strips into boat-access-only properties. Now, a community enjoys a unique lifestyle that blurs the lines between land and water, epitomizing innovation in how we think about living spaces.&lt;/p&gt;
&lt;p&gt;Curious about this fascinating community? Check out the full article to learn more!&lt;/p&gt;
&lt;p&gt;scheendijk&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.core77.com/posts/144869&quot;&gt;Continue reading on &lt;strong&gt;www.core77.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;/p&gt;</content>
    <published>2026-09-30T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/the-dutch-community-where-people-live-on-strips-of-land-in-a-lake</id>
    <title>🔗 The Dutch community where people live on strips of land in a lake</title>
    <updated>2026-09-30T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/your-executable-is-a-sqlite-database" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Can a SQLite database replace the traditional ELF executable format? In a thought-provoking exploration, Farid Zakaria delves into the potential of employing SQLite as a genuine executable, dubbed SELF (Structured Executable &amp; Linkable Format). By leveraging SQLite&apos;s self-describing features, Zakaria argues that an executable format can not only be more efficient but also easier to work with. He demonstrates that key functionalities of ELF can be reimplemented through a relational structure, allowing tools and queries to operate seamlessly without cumbersome overhead. Zakaria&apos;s experiments show that this innovation could streamline program execution while simplifying the complexities typically encountered with ELF files, including dynamic linking and symbol resolution. This article is a detailed journey into a radical idea that blurs the lines between databases and executables, highlighting a forward-thinking approach to software architecture.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://fzakaria.com/2026/08/23/your-executable-is-a-sqlite-database&quot;&gt;Continue reading on &lt;strong&gt;fzakaria.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/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-09-29T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/your-executable-is-a-sqlite-database</id>
    <title>🔗 Your executable is a SQLite database</title>
    <updated>2026-09-29T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/feature-flags-without-a-saas-how-onrotation-gates-features" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;OnRotation is streamlining feature deployment without traditional SaaS solutions. By leveraging &lt;code&gt;Elixir&lt;/code&gt; and &lt;code&gt;Phoenix&lt;/code&gt;, the team implemented a customized feature flag system using a simple table and a function, rather than integrating a more complex library like &lt;code&gt;FunWithFlags&lt;/code&gt;. With a small user base and known testers, the solution simplifies control by allowing specific features to be turned on or off for individuals without requiring a full redeployment of the app. Each flag consists of a unique name, description, and a list of allowed emails, making it both straightforward and manageable. The author emphasizes that this approach fits naturally into the context and architecture of the app, showcasing how a small team can effectively meet their needs without overcomplicating the system.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://nickstalter.com/onrotation-feature-flags&quot;&gt;Continue reading on &lt;strong&gt;nickstalter.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/elixir&quot;&gt;#elixir&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-09-29T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/feature-flags-without-a-saas-how-onrotation-gates-features</id>
    <title>🔗 Feature flags without a SaaS: How OnRotation gates features</title>
    <updated>2026-09-29T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/do-we-still-need-build-tools" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;How necessary are build tools for frontend development in 2026? The article raises crucial questions about their relevance, particularly for CSS and JavaScript. It examines the effectiveness of tools like Autoprefixer, esbuild, and Lightning CSS for managing vendor prefixes and syntax lowering. While some CSS features have become standardized, tools still provide value in combining files and minifying code. The discussion extends to JavaScript, where module bundlers like Webpack and esbuild are highlighted for their performance advantages, despite potential downsides in caching. With HTTP/2 and HTTP/3 changing the landscape, the necessity of bundlers is increasingly debatable. Ultimately, the article argues that build tools still play an essential role, although there are viable no-build alternatives for smaller projects or specific cases.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://olliewilliams.xyz/blog/no-build/&quot;&gt;Continue reading on &lt;strong&gt;olliewilliams.xyz&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/javascript&quot;&gt;#javascript&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/frontend&quot;&gt;#frontend&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/css&quot;&gt;#css&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/tools&quot;&gt;#tools&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-09-29T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/do-we-still-need-build-tools</id>
    <title>🔗 Do we still need build tools?</title>
    <updated>2026-09-29T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/postgresql-for-everything" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Contrary to popular belief, the answer to everything is not 42—it’s PostgreSQL. This article by Dr. Raphael A. Bauer outlines the power and versatility of PostgreSQL, showcasing its use throughout his two-decade career starting in 2003. He highlights its strengths such as being rock-solid, easy to install and scale, and simplifying IT setups by effectively replacing multiple systems. PostgreSQL&apos;s features allow it to function not only as a traditional database but also as a full-text search engine, document storage, and much more. Dr. Bauer discusses various plugins like TimescaleDB and pgvector that extend PostgreSQL’s capabilities, making it suitable for high volume web analytics, AI workflows, and even non-persistent caching. By examining these advantages, he advocates for considering PostgreSQL before looking for other technologies to address new requirements or challenges.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.raphaelbauer.com/posts/postgresql-everything/#postgresql-replaces-solr-and-elastic-full-text-search&quot;&gt;Continue reading on &lt;strong&gt;www.raphaelbauer.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>
    <published>2026-09-28T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/postgresql-for-everything</id>
    <title>🔗 PostgreSQL for everything</title>
    <updated>2026-09-28T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/bun-1-4-rust-rewrite-is-not-looking-good" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Bun, initially a promising project, has faced turmoil during its transition to a Rust-based architecture. Over the past three months, communication has deteriorated into vague promises about version 1.4, with repeated delays frustrating users. Citing over 5,000 open pull requests and heavy reliance on AI, the article highlights concerns about the coding practices adopted during this rewrite. Jarred&apos;s initial capabilities drew admiration, but scrutiny has grown as the codebase has shown signs of instability. The expectation that AI could seamlessly upgrade Bun&apos;s architecture may be misplaced, raising important questions about the future of AI in software development. As users await the next stable release, the sentiment is clear: perception can shift quickly, and trust can erode even faster.&lt;/p&gt;
&lt;p&gt;Based on interviews, many believe that the decision to abandon Zig may have been more about promoting AI capabilities than meeting user needs. With no release in sight, the once-solid foundation of Bun feels precarious.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://tipiirai.com/writing/bun-rust-rewrite-worries&quot;&gt;Continue reading on &lt;strong&gt;tipiirai.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-09-28T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/bun-1-4-rust-rewrite-is-not-looking-good</id>
    <title>🔗 Bun 1.4 Rust rewrite is not looking good</title>
    <updated>2026-09-28T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/how-ai-text-watermarking-works-a-visual-guide" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;A watermark in plain text may seem impossible, as text lacks pixels and metadata. However, Google has implemented text watermarking from Gemini, starting in 2024, with new Claude models marking text invisibly and resiliently as of August 2026. These marks reside in the choices between words, not within the characters themselves.&lt;/p&gt;
&lt;p&gt;The process involves small word choices made by a model that rolls weighted dice among acceptable options. Each choice can secretly lean toward certain words using a key, which makes counting colored choices easier for detection. The text can still read normally, but marked sections show an imbalance when re-evaluated with the correct key. Even editing alters the marks, as they depend on unbroken runs of original text.&lt;/p&gt;
&lt;p&gt;Detection remains private and needs the provider’s key, contrasting with unreliable AI style detectors. This method can indicate whether a text has been processed without confirming authorship. Overall, it highlights the ongoing battle in maintaining and detecting AI-generated information.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://declaude.org/watermarking/&quot;&gt;Continue reading on &lt;strong&gt;declaude.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/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-09-28T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/how-ai-text-watermarking-works-a-visual-guide</id>
    <title>🔗 How AI text watermarking works: a visual guide</title>
    <updated>2026-09-28T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/elixirs-genstage-demand-a-visual-explainer" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;GenStage is a powerful Elixir abstraction that manages data processing through a simple yet effective concept: demand. As articulated by Andrea Leopardi, the article delves into how GenStage enables efficient data flow between producers and consumers while tackling a common issue in concurrent systems—the problem of unbounded queues. The discussion begins with a real-world example involving message consumption from a queue, illustrating how demand controls the rate at which producers send data. By employing a simple demand structure, consumers can regulate their intake and prevent overwhelming the system. The examination highlights how demand helps manage resources and explores important parameters like &lt;code&gt;max_demand&lt;/code&gt; and &lt;code&gt;min_demand&lt;/code&gt;, which dictate the rhythm of event processing. With clear explanations and practical examples, the piece offers vital insights for those looking to harness the full potential of GenStage in their applications.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://andrealeopardi.com/posts/genstage-demand-visualized/&quot;&gt;Continue reading on &lt;strong&gt;andrealeopardi.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/pattern&quot;&gt;#pattern&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/elixir&quot;&gt;#elixir&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-09-27T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/elixirs-genstage-demand-a-visual-explainer</id>
    <title>🔗 Elixir&apos;s GenStage demand (a visual explainer)</title>
    <updated>2026-09-27T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/the-elixir-hiring-paradox-notes-from-elixirconf-eu-2026" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Three common hiring mistakes plague companies looking for Elixir engineers. Arjun Gillard shared insights from his lightning talk at ElixirConf EU 2026 in Málaga, emphasizing that successful hiring requires a clear definition of success in the first 90 days. He noted that recruiters often fail to recognize that volume of applicants doesn&apos;t equal quality, and that evaluating candidates based solely on years of experience in Elixir technologies like Phoenix and LiveView misses the more crucial aspect: an applicant&apos;s reasoning skills. With Elixir&apos;s talent pool being tight-knit and relatively small in Europe, word travels fast when companies implement poor hiring processes. Gillard&apos;s observations highlight the importance of thoughtful, community-driven recruitment strategies that engage with candidates&apos; conceptual understanding rather than their memorized skills in the stack.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://agtalent.co.uk/the-elixir-hiring-paradox-notes-from-elixirconf-eu-2026/&quot;&gt;Continue reading on &lt;strong&gt;agtalent.co.uk&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/elixir&quot;&gt;#elixir&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-09-27T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/the-elixir-hiring-paradox-notes-from-elixirconf-eu-2026</id>
    <title>🔗 The Elixir hiring paradox: notes from ElixirConf EU 2026</title>
    <updated>2026-09-27T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/japan-tried-to-build-an-operating-system-for-the-entire-world-then-the-us-government-intervened" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;There&apos;s an alternate history of computing where Windows wasn&apos;t the dominant OS. This article reveals how Japan&apos;s TRON project aimed to replace traditional file systems with a hypermedia document model, but U.S. government intervention labeled it a trade barrier in 1989. Designed by Ken Sakamura at the University of Tokyo in 1984, TRON included sub-architectures like BTRON for personal computing and ITRON for embedded systems. Despite the ambitious goal of integrating Japan&apos;s digital infrastructure, BTRON was ultimately sidelined. Its design features, like a unique document-centric interface and a character encoding system capable of supporting over a million characters, were years ahead of their time. ITRON, however, succeeded in becoming widely used in embedded systems, marking a significant yet often overlooked chapter in technology history and highlighting the impact of global market dynamics on innovation.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.xda-developers.com/japan-tried-build-operating-system-entire-world-us-government-intervened/&quot;&gt;Continue reading on &lt;strong&gt;www.xda-developers.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;/p&gt;</content>
    <published>2026-09-26T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/japan-tried-to-build-an-operating-system-for-the-entire-world-then-the-us-government-intervened</id>
    <title>🔗 Japan tried to build an operating system for the entire world, then the US government intervened</title>
    <updated>2026-09-26T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/a-struct-is-just-a-map-with-rules" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Elixir&apos;s structs are more than just advanced maps; they enforce rules that prevent typographical errors. When modeling data, like a user profile, using a map can lead to subtle bugs if a key is misspelled — Elixir won&apos;t catch it. Bruce Tate points out that structs enable you to define specific keys within a module, allowing the compiler to enforce structure and prevent mistakes. Each struct contains an extra &lt;code&gt;__struct__&lt;/code&gt; key that links it to the module&apos;s definitions, ensuring the correct framework is maintained. By contrasting maps and structs, Tate emphasizes that maps are useful for dynamic and flexible data, while structs are designed for fixed data types. This nuanced distinction helps developers make informed choices when structuring Elixir applications, aligning with best practices seen within Elixir&apos;s own modules. Using structs can significantly improve code reliability and clarity.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://grox.io/blog/46-a-struct-is-just-a-map-with-rules/&quot;&gt;Continue reading on &lt;strong&gt;grox.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/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/elixir&quot;&gt;#elixir&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-09-26T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/a-struct-is-just-a-map-with-rules</id>
    <title>🔗 A struct is just a map with rules</title>
    <updated>2026-09-26T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/the-reality-of-being-a-cto" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;What does being a CTO really entail? James Stanier reveals that the role is often misunderstood. It ranges from a hands-on founder writing code to a board-level executive. The unique challenges include balancing technology with business outcomes and navigating high-stakes conversations beyond engineering. Stanier emphasizes that a successful CTO must bridge the gap between technical prowess and executive responsibility. He shares insights on managing time between team collaboration and conversations with other functional leaders, which is crucial for operating effectively. The evolving nature of AI introduces additional complexities, as it shifts hiring practices and expectations. Ultimately, being a CTO requires strong financial acumen and the ability to prioritize organizational strategy over just technical excellence.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://leaddev.com/leadership/the-reality-of-being-a-cto&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/ai&quot;&gt;#ai&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-09-26T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/the-reality-of-being-a-cto</id>
    <title>🔗 The reality of being a CTO</title>
    <updated>2026-09-26T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/full-text-search-at-contentful-just-got-faster-why-its-important-and-how-we-did-it" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Full-text search in Contentful just got faster — we improved the median response time by 35%. This is the story of how we did it and why it&apos;s important.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.contentful.com/blog/contentful-faster-full-text-search/&quot;&gt;Continue reading on &lt;strong&gt;www.contentful.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-09-25T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/full-text-search-at-contentful-just-got-faster-why-its-important-and-how-we-did-it</id>
    <title>🔗 Full-text search at Contentful just got faster: Why it’s important and how we did it</title>
    <updated>2026-09-25T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/re-linking-patchwork-with-sashiko" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;On July 14, 2026, Linus Torvalds expressed strong opinions about the role of AI in the Linux kernel development process. He countered the notion of an anti-AI stance within the community, making it clear that AI tools, including LLMs, can enhance the work of maintainers rather than hinder it. Torvalds emphasized that dismissing AI outright fails to recognize its utility and that the kernel community prioritizes technological merit above all. He noted that while AI isn&apos;t flawless, its capabilities have reached a level where it is undeniably beneficial to the project. He urged contributors to embrace these tools and focus on how they can assist rather than complicate development workflows. Torvalds remains committed to a technology-driven approach for the kernel, rejecting any viewpoints based purely on ideological objections.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://lore.kernel.org/linux-media/CAHk-=wi4zC+Ze8e+p3tMv8TtG_80KzsZ1syL9anBtmEh5Z40vg@mail.gmail.com/&quot;&gt;Continue reading on &lt;strong&gt;lore.kernel.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;a href=&quot;https://www.yellowduck.be/tags/ai&quot;&gt;#ai&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-09-25T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/re-linking-patchwork-with-sashiko</id>
    <title>🔗 Re: Linking Patchwork with Sashiko?</title>
    <updated>2026-09-25T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/go-1-27-release-notes" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Go 1.27 has arrived with significant toolchain, runtime, and library updates. It introduces support for generic methods, allowing methods to declare their own type parameters, promoting better data type encapsulation. The &lt;code&gt;math/rand/v2&lt;/code&gt; module now has a generic method signature. Additionally, the release enhances package tools like response file parsing for smoother builds, while deprecating support for &lt;code&gt;bzr&lt;/code&gt; version control. In terms of testing and documentation, &lt;code&gt;go test&lt;/code&gt; now performs a standard library version check by default, and &lt;code&gt;go doc&lt;/code&gt; introduces new syntax for package documentation. It also brings improvements to memory allocation processes and introduces new profiling options, specifically for identifying leaked goroutines. Notably, the addition of new libraries, including &lt;code&gt;encoding/json/v2&lt;/code&gt; and &lt;code&gt;crypto/mldsa&lt;/code&gt;, further enriches the Go ecosystem with modernized functionalities. With Go 1.27, programmers can expect an overall improved experience while maintaining compatibility with previous versions.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://go.dev/doc/go1.27&quot;&gt;Continue reading on &lt;strong&gt;go.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/golang&quot;&gt;#golang&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/announcement&quot;&gt;#announcement&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-09-25T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/go-1-27-release-notes</id>
    <title>🔗 Go 1.27 release notes</title>
    <updated>2026-09-25T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/how-instacart-built-a-modern-search-infrastructure-on-postgres" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;In a previous blog post &lt;a href=&quot;https://tech.instacart.com/optimizing-search-relevance-at-instacart-using-hybrid-retrieval-88cb579b959c&quot;&gt;“Improving search at Instacart using hybrid recall”&lt;/a&gt;, we shared our progress on adaptively combining traditional full text search with embedding-based retrieval. Embarking on this journey required rethinking our search infrastructure to support hybrid recall while ensuring scalability and reliability. In this blog post, we will dive deeper into the architecture and engineering efforts that made this possible and lessons learned along the way.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://tech.instacart.com/how-instacart-built-a-modern-search-infrastructure-on-postgres-c528fa601d54&quot;&gt;Continue reading on &lt;strong&gt;tech.instacart.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/postgresql&quot;&gt;#postgresql&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-09-24T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/how-instacart-built-a-modern-search-infrastructure-on-postgres</id>
    <title>🔗 How Instacart built a modern search infrastructure on PostgreSQL</title>
    <updated>2026-09-24T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/building-distributed-systems-in-elixir-part-5-supervisor-from-scratch" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;In the latest installment of his series, the article breaks down how to create a supervisor from scratch in Elixir, emphasizing the concepts of process links and exit signals. The author illustrates the implementation of a manual supervisor managing two worker processes, highlighting its ability to restart failed workers without affecting healthy ones. The restart policy is simplified to focus only on abnormal exits, mimicking some of the mechanisms provided by OTP without using its built-in features. Through concrete examples, the piece clarifies how to track child processes and respond appropriately to crashes while maintaining the system&apos;s resilience. This hands-on approach aids in understanding distributed systems, making the complexities of supervision more approachable for Elixir developers.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://dev.to/pckrishnadas88/building-distributed-systems-in-elixir-part-5-supervisor-from-scratch-32mh&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/pattern&quot;&gt;#pattern&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/elixir&quot;&gt;#elixir&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-09-24T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/building-distributed-systems-in-elixir-part-5-supervisor-from-scratch</id>
    <title>🔗 Building distributed systems in Elixir: Part 5 — Supervisor from scratch</title>
    <updated>2026-09-24T13:00:00Z</updated>
  </entry>
</feed>