<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog on Rachel Snijders</title>
    <link>https://rachelsnijders.nl/blog/</link>
    <description>Recent content in Blog on Rachel Snijders</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 10 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rachelsnijders.nl/blog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AI is actually good at writing code. I wish it wasn’t.</title>
      <link>https://rachelsnijders.nl/blog/back-to-programming/</link>
      <pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://rachelsnijders.nl/blog/back-to-programming/</guid>
      <description>&lt;p&gt;I am writing this at what I hope is the peak of AI assisted software engineering. Anthropic’s Fable 5 has just released, and somewhere deep down I am glad it’s ridiculously expensive.&lt;/p&gt;&#xA;&lt;p&gt;On the one hand, it has never been easier to build that bespoke application you’ve always wanted, or to solve an esoteric bug in a huge codebase that’s actually costing your company real money every second that it persists. But on the other hand, it feels like the art of programming is slowly disappearing. Not because we don’t &lt;em&gt;want&lt;/em&gt; to put in the effort — but more so because the architecture you would’ve jammed out in your editor during a 4-hour non-stop coding session, fuelled only by coffee and an insatiable desire to build something nice, can also be vibe-coded in fifteen minutes. With some extra prompting, exactly how you would’ve done it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Why I wrote my blog in HUGO, and you should too</title>
      <link>https://rachelsnijders.nl/blog/wrote-blog-in-hugo/</link>
      <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
      <guid>https://rachelsnijders.nl/blog/wrote-blog-in-hugo/</guid>
      <description>&lt;p&gt;I finally have a blog. It runs on &lt;a href=&#34;https://gohugo.io&#34; target=&#34;blank&#34;&gt;Hugo&lt;/a&gt;. The build takes 18 milliseconds. The output is a folder of HTML files I could open in Lynx if I felt like punishing myself. There is no &lt;code&gt;node_modules&lt;/code&gt;. There is no client-side router. There is no spinner.&lt;/p&gt;&#xA;&lt;p&gt;You should do this too. Especially if your current blog is WordPress with 500 plugins.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-thing-nobody-wants-to-admit&#34;&gt;The thing nobody wants to admit&lt;/h2&gt;&#xA;&lt;p&gt;The modern web is unbelievably bloated. Your “lightweight” personal blog probably ships 400 KB of JavaScript before it shows you a single sentence. It has a service worker. It has analytics for the analytics. The first paint waits on a hydration step that exists because someone, somewhere, decided that rendering HTML on a server was a problem that needed solving.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Some smartphone brands to look out for</title>
      <link>https://rachelsnijders.nl/blog/smartphone-brands/</link>
      <pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://rachelsnijders.nl/blog/smartphone-brands/</guid>
      <description>&lt;p&gt;The mobile device market is a duopoly with a thin layer of decoration on top. Apple owns one half. Google owns the other half through Android, even when you’re using a phone with a Samsung sticker on it. Almost everything you can buy in a phone shop in 2026 ships with one of those two operating systems and pours your data back to one of those two companies, often both, by default.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
