<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Glitches Blog</title>
    <link>https://glitches.studionope.nl/blog</link>
    <atom:link href="https://glitches.studionope.nl/feed.xml" rel="self" type="application/rss+xml" />
    <description>Practical guides on filing better bug reports — GitHub templates, screen recording workflows, and the AI auto-fix pipeline that turns a screenshot into a pull request.</description>
    <language>en</language>
    <lastBuildDate>Mon, 04 May 2026 12:37:21 GMT</lastBuildDate>
    <item>
      <title>How to Write a Bug Report Developers Will Act On</title>
      <link>https://glitches.studionope.nl/blog/how-to-write-a-bug-report</link>
      <guid isPermaLink="true">https://glitches.studionope.nl/blog/how-to-write-a-bug-report</guid>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
      <dc:creator>Bas Fijneman</dc:creator>
      <description>How to write a bug report developers actually pick up. Five-section structure, title craft, and the expected-vs-actual trick that ships fixes faster — anchored in NN/g&apos;s reading-pattern research and Cem Kaner&apos;s bug-advocacy framework.</description>
    </item>
    <item>
      <title>Bug Report Template for GitHub — Copy-Paste Markdown</title>
      <link>https://glitches.studionope.nl/blog/bug-report-template-github</link>
      <guid isPermaLink="true">https://glitches.studionope.nl/blog/bug-report-template-github</guid>
      <pubDate>Thu, 30 Apr 2026 00:00:00 GMT</pubDate>
      <dc:creator>Bas Fijneman</dc:creator>
      <description>GitHub bug report template, copy-paste ready. Markdown and YAML Issue Forms for any repo, plus the why behind every field — citing Joel Spolsky, Mozilla&apos;s Bug Writing Guidelines, and GitHub&apos;s official docs.</description>
    </item>
  </channel>
</rss>
