<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tom Hinsley — Blog</title>
    <link>https://www.tomhinsley.com/blog</link>
    <atom:link href="https://www.tomhinsley.com/feed.xml" rel="self" type="application/rss+xml" />
    <description>Notes, essays and dev logs. Mostly about whatever I’m currently chewing on, usually code, sometimes audio, occasionally a book.</description>
    <language>en-GB</language>
    <item>
      <title>I came to code the long way round</title>
      <link>https://www.tomhinsley.com/blog/the-long-way-round</link>
      <guid>https://www.tomhinsley.com/blog/the-long-way-round</guid>
      <pubDate>Mon, 29 Jun 2026 00:00:00 GMT</pubDate>
      <description>Sound first, then film, then code. How I came to building for the web the long way round, and why all of it now lives in one place.</description>
    </item>
    <item>
      <title>Is Tailwind the best way to write styles, now the AI reads everything?</title>
      <link>https://www.tomhinsley.com/blog/scss-or-tailwind-with-ai</link>
      <guid>https://www.tomhinsley.com/blog/scss-or-tailwind-with-ai</guid>
      <pubDate>Thu, 04 Jun 2026 00:00:00 GMT</pubDate>
      <description>An assistant types most of the class names now, so the cost that's left is reading them, the model included. I measured the same button styled four ways, Tailwind, CSS Modules, CSS-in-JS and shadcn, and laid out where each one fits. There's no single winner, but the numbers make the trade-offs concrete.</description>
    </item>
  </channel>
</rss>