<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="https://www.yellowduck.be/pretty-atom-feed-v3.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <link href="https://www.yellowduck.be" rel="alternate"/>
  <link href="https://www.yellowduck.be/posts/feed" rel="self"/>
  <author>
    <name>Pieter Claerhout</name>
    <email>pieter@yellowduck.be</email>
  </author>
  <id>https://www.yellowduck.be/posts/feed</id>
  <title>🐥 YellowDuck.be</title>
  <updated>2026-08-02T17:00:00Z</updated>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/the-laravel-scheduler-under-the-hood" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Laravel&apos;s Scheduler features an API that simplifies task scheduling, but its underlying mechanics are crucial to understand. When cron triggers &lt;code&gt;php artisan schedule:run&lt;/code&gt;, Laravel takes over to determine which events are due. This article dives deep into the Laravel Scheduler, explaining how it processes scheduled tasks, from command definitions to execution. It clarifies concepts like &lt;code&gt;onOneServer()&lt;/code&gt; and &lt;code&gt;withoutOverlapping()&lt;/code&gt;, which are essential for managing concurrent tasks. Readers learn how Laravel creates event objects from command definitions and how frequency methods adjust cron expressions. The article emphasizes the distinctions between the Scheduler and the Queue system, underpinning the operational design decisions that make task scheduling effective in production environments. Armed with this insight, Laravel developers can better leverage the Scheduler for reliable task execution.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://wendelladriel.com/blog/the-laravel-scheduler-under-the-hood&quot;&gt;Continue reading on &lt;strong&gt;wendelladriel.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/laravel&quot;&gt;#laravel&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-02T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/the-laravel-scheduler-under-the-hood</id>
    <title>🔗 The Laravel Scheduler Under the Hood</title>
    <updated>2026-08-02T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/waze-now-supports-electric-vehicles-in-belgium" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Finding a charging station for your electric vehicle won&apos;t be difficult anymore. Waze has added full support for electric charging points on its map in Belgium, enabling users to enter their car and plug type. This upgrade allows Waze to pinpoint all available charging points in your vicinity or along your route.&lt;/p&gt;
&lt;p&gt;Thanks to the dedicated volunteer map editors, reliable information on charging points is now accessible. The community has worked tirelessly to update the Waze map with this critical data, ensuring it remains current. To configure electric vehicle support, users can navigate to Settings -&gt; Vehicle Details -&gt; Electric vehicles and toggle the EV features on, allowing them to easily find the nearest charging station. Users can also report outdated charging points for the community editors to review and update accordingly.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.wazebelgium.be/waze-now-supports-electric-vehicles-in-belgium/&quot;&gt;Continue reading on &lt;strong&gt;www.wazebelgium.be&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/announcement&quot;&gt;#announcement&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-02T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/waze-now-supports-electric-vehicles-in-belgium</id>
    <title>🔗 Waze now supports electric vehicles in Belgium</title>
    <updated>2026-08-02T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/claude-code-sends-4-7x-more-tokens-than-opencode-before-reading-your-prompt" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Claude Code&apos;s appetite for tokens far exceeds that of OpenCode, as the article reveals startling figures from direct comparisons. In experiments run under identical conditions, Claude Code averaged around 33,000 tokens for a one-line reply, while OpenCode only consumed about 7,000. The data reported showcases how Claude Code’s approach introduces significant cache inefficiencies, requiring 54 times more tokens for some tasks. A primary concern raised is the impact on production environments, particularly when operating under regulations like the EU AI Act. The emphasis is on understanding the tokens spent is crucial for optimizing agentic AI systems, where every token represents context that can&apos;t be utilized for task completion. Additionally, analyzing not just input but also cache writes reveals the complexity and potential costs associated with these AI harnesses.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://systima.ai/blog/claude-code-vs-opencode-token-overhead&quot;&gt;Continue reading on &lt;strong&gt;systima.ai&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/development&quot;&gt;#development&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/ai&quot;&gt;#ai&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-02T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/claude-code-sends-4-7x-more-tokens-than-opencode-before-reading-your-prompt</id>
    <title>🔗 Claude Code sends 4.7x more tokens than OpenCode before reading your prompt</title>
    <updated>2026-08-02T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/software-has-changed" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;A surprising truth reveals how quickly the software landscape has transformed. In a recent tweet, Jamon Holmgren notes that many experienced engineers feel shell-shocked by these rapid changes. Development cycles are faster, yet there&apos;s a concern about not building the right things. The industry has shifted from deep focus to a management of constant new experiments, allowing for greater code review and refinement.&lt;/p&gt;
&lt;p&gt;Building faster doesn’t mean building better, but it does free up developers to tackle technical debt proactively. Holmgren reflects on this evolution, pondering the implications of how code is created versus its final quality. With the ability to learn and adapt, many are navigating this new landscape while aiming to produce trusted, quality code.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.abeautifulsite.net/posts/software-has-changed/&quot;&gt;Continue reading on &lt;strong&gt;www.abeautifulsite.net&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/development&quot;&gt;#development&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-01T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/software-has-changed</id>
    <title>🔗 Software has changed</title>
    <updated>2026-08-01T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/zig-creator-calls-spade-a-spade-anthropic-blows-smoke" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Anthropic&apos;s ambitious narrative suggests software engineering will vanish, backed by a staggering $132 billion investment and a looming IPO. However, skepticism is essential; with no profitability in sight, decisions based on such hype could lead to misguided architecture and staffing choices driven by fear. Andrew Kelley, the creator of Zig, openly criticized the migration of the Bun project from Zig to Rust, framing it as a marketing ploy rather than a technical necessity. This situation raises questions not only about the software&apos;s future but also about the reliability of narratives shaped by significant financial backing. With Bun’s heavy reliance on AI and the subsequent shift, the community now grapples with the implications of these choices in a world where every programming language is scrutinized against performance and credibility measures. The drama unfolds not just in technical decisions, but in the larger discourse around automation and responsibility in software development.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://raymyers.org/post/zed-creator-calls-spade-a-spade/&quot;&gt;Continue reading on &lt;strong&gt;raymyers.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/rust&quot;&gt;#rust&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/development&quot;&gt;#development&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/ai&quot;&gt;#ai&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-08-01T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/zig-creator-calls-spade-a-spade-anthropic-blows-smoke</id>
    <title>🔗 Zig creator calls spade a spade, Anthropic blows smoke</title>
    <updated>2026-08-01T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/de-morgans-law" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Logical expressions can turn complex quickly, but understanding De Morgan’s Law can simplify them effectively. This principle, attributed to Augustus de Morgan in the 19th century, states that certain expressions using NOT, AND, and OR operations can be rewritten without changing their results. For instance, NOT(A) AND NOT(B) is equivalent to NOT(A OR B). Tracy Gilmore illustrates this concept with practical examples, including a detailed breakdown of truth tables and expressions. The article provides a clear guide on how to apply De Morgan’s Law to make code more readable and efficient. It&apos;s a valuable resource for programmers looking to improve their logical condition handling and streamline their code without the harsh symbols of Boolean algebra. Gilmore’s straightforward explanations make the law accessible for both seasoned developers and those newer to coding.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://dev.to/tracygjg/de-morgans-law-a-little-computer-science-for-the-inquisitive-developer-4m2k&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>
    <published>2026-08-01T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/de-morgans-law</id>
    <title>🔗 De Morgan’s Law</title>
    <updated>2026-08-01T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/the-order-of-data-defaults-performance-determinism-paging" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;What happens when an SQL query doesn&apos;t specify the &lt;code&gt;ORDER BY&lt;/code&gt; clause? This article breaks down the consequences of relying on the default sorting behavior across different databases such as Postgres, MySQL, and MongoDB. It illustrates with detailed SQL operations how Postgres defaults to insertion order, while MySQL may sort rows by primary key. It also points out the risks of assuming that the default order will remain consistent after updates or deletions. The author emphasizes that each database&apos;s handling of data ordering can affect performance and predictability, making it crucial for developers to be explicit in their ordering strategy.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://binaryigor.com/the-order-of-data.html&quot;&gt;Continue reading on &lt;strong&gt;binaryigor.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/sql&quot;&gt;#sql&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-07-31T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/the-order-of-data-defaults-performance-determinism-paging</id>
    <title>🔗 The Order of Data: defaults, performance, determinism &amp; paging</title>
    <updated>2026-07-31T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/small-programming-tricks" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Small nuggets of knowledge can significantly enhance engineering productivity. This article reveals useful programming tricks that don&apos;t require extensive prior knowledge. For instance, using &lt;code&gt;python3 -m http.server&lt;/code&gt; for quickly starting a simple server is highlighted. The author also suggests tools like &lt;code&gt;fzf&lt;/code&gt; for fuzzy searching terminal history, &lt;code&gt;atuin&lt;/code&gt; for a searchable SQLite database of shell history, and practical database commands such as &lt;code&gt;SELECT&lt;/code&gt; without a &lt;code&gt;FROM&lt;/code&gt;. Techniques in regular expressions, modern JavaScript capabilities, and efficient &lt;code&gt;git&lt;/code&gt; commands are discussed as well. These tricks emphasize that even minor insights can lead to substantial efficiency gains in programming tasks. Sharing these nuggets within teams can foster a culture of learning and continuous improvement. Inspired by Julia Evan&apos;s approach, the article emphasizes that small bits of knowledge are both powerful and enjoyable to learn.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://will-keleher.com/posts/small-programming-tricks-matter/&quot;&gt;Continue reading on &lt;strong&gt;will-keleher.com&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/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/tools&quot;&gt;#tools&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/terminal&quot;&gt;#terminal&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/git&quot;&gt;#git&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-07-31T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/small-programming-tricks</id>
    <title>🔗 Small programming tricks</title>
    <updated>2026-07-31T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/lucas-laws-of-project-management" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;A project’s success hinges on solving the actual problem, rather than solely adhering to a specification. Surprisingly, compliance with the initial scope is often misguided because the primary focus should be on user needs. As a project unfolds, the understanding of the problem evolves, necessitating adaptations in the solution. Prioritizing problem comprehension over rigid scope planning is key. As the article outlines, assumptions must be tested not for their ease but based on their potential cost if proven wrong. It emphasizes the importance of clear communication and shared understanding within the team, advocating for a streamlined backlog and adaptable plans. This method ensures that projects remain viable, meet deadlines, and continuously provide value throughout their lifecycle.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://lucasfcosta.com/blog/laws-of-software-project-management&quot;&gt;Continue reading on &lt;strong&gt;lucasfcosta.com&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/development&quot;&gt;#development&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-07-31T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/lucas-laws-of-project-management</id>
    <title>🔗 Lucas&apos; Laws of Project Management</title>
    <updated>2026-07-31T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/go-flavored-concurrency-in-c" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Go&apos;s concurrency model is attractive, but can it be mimicked in C using POSIX threads? This article delves into that question, exploring how to forge Go-like concurrency in C without runtime support and garbage collection. The writer introduces &lt;code&gt;Solod&lt;/code&gt;, a strict Go subset that compiles to C, utilizing POSIX thread constructs such as mutexes and condition variables as its foundation.&lt;/p&gt;
&lt;p&gt;The piece details various concurrency mechanisms like atomics, the worker pool, and task scheduling. Specific code snippets illustrate the direct translations from So to C, shedding light on performance trade-offs inherent to using OS threads versus lightweight goroutines. The core takeaway is clear: while achieving Go-like concurrency in C is challenging due to the shortcomings of POSIX threads, significant capabilities remain realizable by leveraging the right primitives and accepting the associated trade-offs.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://antonz.org/concurrency-in-c/&quot;&gt;Continue reading on &lt;strong&gt;antonz.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/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/pattern&quot;&gt;#pattern&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-07-30T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/go-flavored-concurrency-in-c</id>
    <title>🔗 Go-flavored concurrency in C</title>
    <updated>2026-07-30T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/my-ai-learning-journey" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Metrics have always been the so-called magic beans for improving quality in testing and quality engineering. In her article, Lisa Crispin emphasizes the importance of measuring AI success and quality improvement. She shares her decades of experience in the field and highlights how continuous quality improvement is crucial for modern software teams. The discussion revolves around effective metrics that can drive quality initiatives, making the case for an analytical approach to testing. Crispin brings a fresh perspective on harnessing metrics to elevate both AI performance and overall product quality.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://lisacrispin.com/2026/07/10/my-ai-learning-journey/&quot;&gt;Continue reading on &lt;strong&gt;lisacrispin.com&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/best-practice&quot;&gt;#best-practice&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/ai&quot;&gt;#ai&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/testing&quot;&gt;#testing&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-07-30T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/my-ai-learning-journey</id>
    <title>🔗 My AI learning journey</title>
    <updated>2026-07-30T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/good-tools-are-delightful" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Good tools are designed with the user&apos;s needs in mind, leading to unexpected delight and increased productivity. Zach Daniel emphasizes how tools like Neovim create opportunities for learning and improvement, rather than simply fading into the background. He reflects on his own experience with plugins such as Neogit, which enhanced his understanding and efficiency in managing code. Daniel critiques the idea that effective tools should be invisible, arguing instead for tools that challenge users to grow. He also touches on the evolving landscape of tools with the rise of LLMs, noting their potential to streamline workflows without sacrificing depth. Ultimately, he champions the view that while good tools may disappear, the best ones empower and delight users.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.zachdaniel.dev/p/good-tools-are-delightful&quot;&gt;Continue reading on &lt;strong&gt;www.zachdaniel.dev&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/development&quot;&gt;#development&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/tools&quot;&gt;#tools&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/ai&quot;&gt;#ai&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-07-30T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/good-tools-are-delightful</id>
    <title>🔗 Good tools are delightful</title>
    <updated>2026-07-30T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/two-database-migrations-and-a-divorce" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Jack Ellis narrates the journey of migrating Fathom Analytics to a new database structure while eliminating significant technical debt. This complex project, which involved moving over 65 billion rows, was accomplished by a single engineer. Ellis discusses the challenges faced, particularly concerning cookie laws, user privacy, and the evolution of their data ingestion model. A pivotal moment arose when they concluded that traditional methods of tracking unique visitors could not align with emerging privacy standards. The team innovated with daily salts and hashing, paving the way for a privacy-first approach in analytics. However, years of technical debt complicated their architecture, leading to issues like broken queries and inability to scale. The article provides detailed insights into the considerations and decisions that shaped this significant migration, reflecting on lessons learned and how they evolved their analytics solutions for better performance and privacy.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://usefathom.com/blog/two-database-migrations-and-a-divorce&quot;&gt;Continue reading on &lt;strong&gt;usefathom.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-07-29T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/two-database-migrations-and-a-divorce</id>
    <title>🔗 Two database migrations and a divorce</title>
    <updated>2026-07-29T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/claude-md-is-ram-not-disk" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Claude.md serves as working memory that needs to stay concise to remain effective. Alberto Arena highlights the pitfalls of allowing it to grow unwieldy, leading to reduced performance. Instead of cramming all information into this singular file, he advocates using it for essential, frequently required commands and pointers, while storing less frequently accessed information in separate documents. This distinction helps Claude manage context more efficiently and reduces unnecessary cognitive load. Applying this strategy means better interaction with the AI, as it has immediate access to crucial data while longer-term documentation resides in designated locations, unfettered by the immediate operational needs. Simplifying the architecture around how data is organized can significantly enhance coding workflows, especially in significant frameworks like Laravel.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://albertoarena.it/posts/claude-md-is-ram-not-disk/&quot;&gt;Continue reading on &lt;strong&gt;albertoarena.it&lt;/strong&gt;&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://www.yellowduck.be/tags/reading-list&quot;&gt;#reading-list&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/laravel&quot;&gt;#laravel&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/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-07-29T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/claude-md-is-ram-not-disk</id>
    <title>🔗 Claude.md is RAM, not disk</title>
    <updated>2026-07-29T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/i-think-i-have-llm-burnout" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Is burnout from large language models (LLMs) a real issue? The article reflects on the author&apos;s heavy usage of LLMs like Claude Code and Codex for daily tasks, expressing both productivity gains and mounting frustrations. After a year of constant interaction with AI-generated content, the author finds themselves increasingly annoyed by repetitive patterns, inaccuracies, and the overall style of LLM output—leading to feelings of fatigue towards these tools. Despite the productivity benefits, they acknowledge a shift in their disposition, grappling with the challenge of managing expectations and the limitations of LLMs. While the fascination remains, the growing irritation complicates their experience and relationship with AI.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.alecscollon.com/blog/llm-burnout/&quot;&gt;Continue reading on &lt;strong&gt;www.alecscollon.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-07-29T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/i-think-i-have-llm-burnout</id>
    <title>🔗 I think I have LLM burnout</title>
    <updated>2026-07-29T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/http-query-method-support-in-laravel-13-19" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Laravel 13.19.0 introduces support for the HTTP QUERY method across its HTTP client and testing helpers. The new &lt;code&gt;Http::query()&lt;/code&gt; method allows users to issue QUERY requests, sending parameters in the request body rather than the URL. This mirrors existing methods like &lt;code&gt;post()&lt;/code&gt;, &lt;code&gt;put()&lt;/code&gt;, and &lt;code&gt;patch()&lt;/code&gt; and defaults to sending JSON data.&lt;/p&gt;
&lt;p&gt;The article also covers new testing helpers: &lt;code&gt;query()&lt;/code&gt; and &lt;code&gt;queryJson()&lt;/code&gt;, which facilitate testing routes that respond to QUERY requests. Additionally, a new collection method, &lt;code&gt;reduceInto()&lt;/code&gt;, is introduced for more effective accumulator handling. Other enhancements include the &lt;code&gt;counted()&lt;/code&gt; string helper to streamline word pluralization, bulk SQS dispatch improvements, and numerous bug fixes and optimizations. This release reflects Laravel&apos;s commitment to evolving and refining its framework.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://laravel-news.com/laravel-13-19-0&quot;&gt;Continue reading on &lt;strong&gt;laravel-news.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/laravel&quot;&gt;#laravel&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/php&quot;&gt;#php&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/http&quot;&gt;#http&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/testing&quot;&gt;#testing&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-07-28T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/http-query-method-support-in-laravel-13-19</id>
    <title>🔗 HTTP query method support in Laravel 13.19</title>
    <updated>2026-07-28T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/tower-17-for-mac-beta-smarter-fully-merged-detection" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Tower 17 for Mac, now in Beta, introduces significantly smarter &quot;Fully Merged&quot; detection. This update allows Tower to match local branches against merged pull requests from hosting services like GitHub and GitLab. Previously, users faced uncertainty when deleting branches that were squash or rebase merged, leading to cluttered projects with irrelevant branches. With this release, Tower employs advanced checks, including Git&apos;s classic merge detection and merge commit analysis, to accurately identify if branches are fully merged.&lt;/p&gt;
&lt;p&gt;The redesigned hint view enhances transparency, showing exactly which checks applied when determining if a branch can be safely deleted. Users can also quickly access merge commits or pull requests for verification. Additional improvements enhance the application’s performance, particularly in updating submodules. Tower&apos;s new features aim to streamline users&apos; workflows and make branch management safer and more intuitive.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.git-tower.com/blog/tower-mac-17&quot;&gt;Continue reading on &lt;strong&gt;www.git-tower.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/tools&quot;&gt;#tools&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/git&quot;&gt;#git&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/mac&quot;&gt;#mac&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-07-28T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/tower-17-for-mac-beta-smarter-fully-merged-detection</id>
    <title>🔗 Tower 17 for Mac (Beta) — smarter &quot;fully merged&quot; detection</title>
    <updated>2026-07-28T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/announcing-typescript-7-0" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;TypeScript 7 has arrived, boasting a native port that is reported to be 10 times faster than its predecessor. This major rewrite was done in Go, allowing it to leverage modern hardware effectively. Developers can expect significant speedups in various operations like &lt;code&gt;find-all-references&lt;/code&gt;, auto-completions, and diagnostics, with build times seeing improvements between 8x and 12x on common open-source projects. Notably, TypeScript 7 is designed for seamless integration with popular editors such as VS Code and Visual Studio. Initial tests reveal the new version reduces memory usage while enhancing responsiveness. Major companies, including Google and Microsoft, have tested and adopted TypeScript 7, reporting drastically improved performance. As it currently stands, TypeScript 7 can run alongside version 6, ensuring a smooth transition for ongoing projects. Tight feedback loops and aggressive testing have also bolstered quality, making this release one of the most stable yet.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/&quot;&gt;Continue reading on &lt;strong&gt;devblogs.microsoft.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/typescript&quot;&gt;#typescript&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/announcement&quot;&gt;#announcement&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-07-27T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/announcing-typescript-7-0</id>
    <title>🔗 Announcing TypeScript 7.0</title>
    <updated>2026-07-27T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/the-four-horsemen-behind-thousands-of-postgres-outages" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Postgres outages often stem from preventable issues related to vacuum operations, connection limits, and query planning. Many startups face downtime due to insufficient handling of transaction ID wraparound and I/O competition caused by vacuum processes. The author highlights innovative solutions through &lt;code&gt;pgrust&lt;/code&gt;, a reimplementation of Postgres, which aims to offer a modern architecture, including 64-bit transaction IDs and thread-based processing for better resource management. The article emphasizes the challenges posed by bad query plans and the need for improved JSON handling, acknowledging the frustrations caused by the existing limitations in Postgres. This proactive approach promises to address common pain points faced by users in real-world applications.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://malisper.me/the-four-horsemen-behind-thousands-of-postgres-outages/&quot;&gt;Continue reading on &lt;strong&gt;malisper.me&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;a href=&quot;https://www.yellowduck.be/tags/devops&quot;&gt;#devops&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-07-27T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/the-four-horsemen-behind-thousands-of-postgres-outages</id>
    <title>🔗 The four horsemen behind thousands of Postgres outages</title>
    <updated>2026-07-27T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/old-icons" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;What do old Mac application icons reveal about design constraints? In a recent piece, Dr. Drang reflects on the evolution of Mac icons, revisiting the early days where icons were merely 32x32 pixel images, often in black and white. Inspired by a call to “Free the Icons,” he explores how classic designs like those for MacWrite and MacPaint utilized simple shapes like tilted rectangles and hand motifs to convey their functions. This look back highlights how design limitations led to creative solutions, illustrating a whimsical era of iconography that has since been constrained by modern standards. Dr. Drang contrasts today’s “squircle jail” with the more playful, distinctive features of early icons, offering a nostalgic glimpse into a transformative period in software design.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://leancrew.com/all-this/2026/07/old-icons/&quot;&gt;Continue reading on &lt;strong&gt;leancrew.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/mac&quot;&gt;#mac&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-07-27T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/old-icons</id>
    <title>🔗 Old icons</title>
    <updated>2026-07-27T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/livestash-performance-tests" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;LiveView is an amazing Elixir framework, but what happens when your connection drops? Krzysztof Nalepa and Filip Węgrzyn dive into the challenges faced with state management during reconnections in Phoenix LiveView applications. They present the LiveStash library, which addresses these issues by persisting LiveView state seamlessly. The article details various adapters for LiveStash, including ETS, Redis, Browser memory, and Mnesia, each with unique strengths and weaknesses.&lt;/p&gt;
&lt;p&gt;To understand how these adapters perform under pressure, the authors designed stress tests using 25,000 virtual users across different Time-To-Live configurations. The results provide valuable insights into memory usage, network throughput, and Erlang process behavior. This testing highlights the critical importance of architecture choices in achieving reliable and efficient state management during user reconnections. The findings serve as a guide for developers looking to optimize their applications with LiveStash.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://swmansion.com/blog/live-stash-performance-tests/&quot;&gt;Continue reading on &lt;strong&gt;swmansion.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/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/testing&quot;&gt;#testing&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-07-26T17:00:00Z</published>
    <id>https://www.yellowduck.be/posts/livestash-performance-tests</id>
    <title>🔗 LiveStash Performance Tests</title>
    <updated>2026-07-26T17:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/watch-exploring-liveview-1-2s-server-composed-js-commands-colocated-css-and-colocated-hooks" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Can your UI logic truly live in Elixir? This article details how to refactor a LiveView trivia game using Phoenix LiveView 1.2&apos;s new features. The author walks through moving UI logic, JavaScript commands, and styles directly into the LiveView, enhancing organization and maintainability. By implementing server-composed JS commands and colocated CSS, changes are made simpler and more intuitive. The refactoring not only maintains functionality but also improves the clarity of how the feedback works on user interactions. Learn practical steps through code snippets and detailed explanations, perfect for those looking to embrace the latest in LiveView development.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://potions.io/blog/colocating-liveview-js-css-and-hooks&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/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/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-07-26T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/watch-exploring-liveview-1-2s-server-composed-js-commands-colocated-css-and-colocated-hooks</id>
    <title>🔗 Watch: Exploring LiveView 1.2&apos;s server-composed JS commands, colocated CSS, and colocated hooks</title>
    <updated>2026-07-26T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/ash-framework-in-11-minutes" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;If you&apos;ve heard of Ash but haven&apos;t tried it, Mateusz Kowalczyk walks through a full example in 11 minutes: modeling resources with attributes and relationships, wiring up actions and policies, then reusing it across Phoenix forms, JSON:API, GraphQL, TypeScript, and AI tools.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://www.youtube.com/watch?v=dDP1I2d3CB4&quot;&gt;Continue reading on &lt;strong&gt;www.youtube.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/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-07-26T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/ash-framework-in-11-minutes</id>
    <title>🔗 Ash Framework in 11 minutes</title>
    <updated>2026-07-26T08:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/mastering-linux-administration-20-powerful-commands-to-know" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;Linux administrators can sometimes overlook essential commands that significantly enhance system management. From monitoring system performance to network diagnostics, the article outlines 20 powerful Linux commands every admin should know. Key commands like &lt;code&gt;vmstat&lt;/code&gt;, &lt;code&gt;inotifywait&lt;/code&gt;, and &lt;code&gt;ncdu&lt;/code&gt; are covered, providing insights into their functions and examples of usage. For instance, &lt;code&gt;vmstat&lt;/code&gt; reveals insights into memory usage, while &lt;code&gt;inotifywait&lt;/code&gt; monitors file changes in real-time. This collection aims to equip users with knowledge that can streamline administration tasks and improve overall Linux performance, making it a great resource for both novice and experienced users.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://linuxblog.io/mastering-linux-administration-20-powerful-commands-to-know/&quot;&gt;Continue reading on &lt;strong&gt;linuxblog.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/best-practice&quot;&gt;#best-practice&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/terminal&quot;&gt;#terminal&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/linux&quot;&gt;#linux&lt;/a&gt; &lt;a href=&quot;https://www.yellowduck.be/tags/sysadmin&quot;&gt;#sysadmin&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-07-25T13:00:00Z</published>
    <id>https://www.yellowduck.be/posts/mastering-linux-administration-20-powerful-commands-to-know</id>
    <title>🔗 Mastering linux administration: 20 powerful commands to know</title>
    <updated>2026-07-25T13:00:00Z</updated>
  </entry>
  <entry>
    <author>
      <name>Pieter Claerhout</name>
      <email>pieter@yellowduck.be</email>
    </author>
    <link href="https://www.yellowduck.be/posts/daisyui-skill-essential-for-all-daisyui-projects" rel="alternate"/>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;AI coding agents struggle with the nuances of your UI system, especially with tools like daisyUI. The newly introduced &lt;code&gt;daisyUI Skill&lt;/code&gt; equips these agents with vital instructions and context needed to generate refined Tailwind CSS and daisyUI code. With components, themes, color rules, and installation guidelines, agents can avoid common pitfalls and write more fitting UI code without constant prompts. This skill not only streamlines the process but ensures that the output adheres to the design system. By minimizing variability in generated code, &lt;code&gt;daisyUI Skill&lt;/code&gt; leads to easier maintenance and a cohesive look across projects. As AI assistants take center stage in UI generation, having a solid framework like this can make all the difference in building robust applications with daisyUI.&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://daisyui.com/blog/daisyui-skill/&quot;&gt;Continue reading on &lt;strong&gt;daisyui.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/ai&quot;&gt;#ai&lt;/a&gt;&lt;/p&gt;</content>
    <published>2026-07-25T08:00:00Z</published>
    <id>https://www.yellowduck.be/posts/daisyui-skill-essential-for-all-daisyui-projects</id>
    <title>🔗 DaisyUI skill: essential for all daisyUI projects</title>
    <updated>2026-07-25T08:00:00Z</updated>
  </entry>
</feed>